Petascope_Error when creating the duplicate type for cell/mdd/set for a coverage to be reinserted after removing it

[Bang Pham Huu]

After ingesting a coverage and removing it, the cell/mdd/set in rasdaman still exist.

The 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.

This 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.

Here are the duplicated queries to create existing type in Petascope when trying to ingest the same coverage after deleting it.

CREATE TYPE test_ansidate_different_crs_origin_Cell AS ( band0 long ,band1 long  )

and after that, user can update this coverage without problem. But if user restarts petascope, then when trying to update this coverage with wcst_import, it will throw exception

<ows:ExceptionReport version="2.0.1"
    xsi:schemaLocation="http://www.opengis.net/ows/2.0 http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd"
    xmlns:ows="http://www.opengis.net/ows/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink">
    <ows:Exception exceptionCode="RasdamanRequestFailed">
        <ows:ExceptionText>Error evaluating rasdaman query: 'CREATE TYPE test_ansidate_different_crs_origin_Cell AS ( band0 long ,band1 long  )'</ows:ExceptionText>
    </ows:Exception>
</ows:ExceptionReport>

due to this type already exists

rasql -q 'CREATE TYPE test_ansidate_different_crs_origin_Cell AS ( band0 long ,band1 long  )' --user rasadmin --passwd rasadmin
rasql: rasdaman query tool v1.0, rasdaman 9.4.0.
opening database RASBASE at localhost:7001...ok
Executing update query...rasdaman error 969: Update error 969 in line 1, column 1, near token test_ansidate_different_crs_origin_Cell: Type already exists.
aborting transaction...ok