Changes between Initial Version and Version 23 of Ticket #1055


Ignore:
Timestamp:
Jan 7, 2016, 12:00:39 PM (9 years ago)
Author:
Bang Pham Huu
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1055

    • Property Status new → assigned
    • Property Summary wcst_import error with creating new coverage that has been dropped before → error when inserting a new coverage id that is the same name as an existing rasdaman collection
    • Property Keywords petascope added; wcst_import error removed
    • Property Milestone 9.1.x → 9.2

  • Ticket #1055 – Description

    initial v23  
    1  The problem is when I use wcst_import to import some data to rasdaman with coverage id like a, b, c then I drop petascopedb, then I import it again and an error appear. I think this is not consistent in here (it is best that wcst-import not only check in petascopedb but check collection from rasdaman also). Only if both case is not exist then wcst-import can import data or will have error that coverage is exist.
     1'''Modification: ''' This problem happens when a collection has been created in rasdaman database and one using wcst_import to ingest a coverage id with the same as collection name.
     2
     3Example:
     4
     5rasql -q "create collection rgb RGBSet" --user rasadmin --passwd rasadmin
     6
     7wcst_import.sh ingest.json (with "coverage_id": "rgb")
     8
     9
     10The problem is when I use wcst_import to import some data to rasdaman with coverage id like a, b, c then I drop petascopedb, then I import it again and an error appear. I think this is not consistent in here (it is best that wcst-import not only check in petascopedb but check collection from rasdaman also). Only if both case is not exist then wcst-import can import data or will have error that coverage is exist.
    211
    312{{{