Changes between Initial Version and Version 1 of Ticket #1612


Ignore:
Timestamp:
Sep 25, 2017, 12:18:46 PM (7 years ago)
Author:
Bang Pham Huu
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1612

    • Property Summary Petascope_Error when creating the duplicate type for cell/mdd/set after restarting petascope → Petascope_Error when creating the duplicate type for cell/mdd/set for a coverage to be reinserted after removing it

  • Ticket #1612 – Description

    initial v1  
    1 When ingesting a coverage (create first then update), Petascope already created a cell/mdd/set for this collection, e.g:
     1After ingesting a coverage and removing it, the cell/mdd/set in rasdaman still exist.
    22
     3The real problem comes from the way it checks nilValues in Petascope. As NilValue object contain a scalar value and a reason, it is not good to check with a collection can contain this NilValue object with built-it contain method, but need to check the scalar value explicitly.
     4
     5This happens after the patch for ticket 1029 which uses coverageId as base type (cell/array/set), before in this case, it will just create a random string so the error does not appear.
     6
     7Here are the duplicated queries to create existing type in Petascope when trying to ingest the same coverage after deleting it.
    38
    49{{{