problem with duplicate collection names

[Dimitar Misev]

I see a problem with this output (the collection names with timestamp in them), but I'm not sure what could cause it. Any ideas?

  Result object 1: PlanetDEM_30_Plus
  Result object 2: NEXTMap_5_DSM_2016_11_28_13_40_15_8375
  Result object 3: NEXTMap_5_DSM
  Result object 4: OPUS_AFRICA
  Result object 5: NM_CNTRS
  Result object 6: CD_S2
  Result object 7: Sentinel_2
  Result object 8: Pleiades_Demo
  Result object 9: NM
  Result object 10: Sentinel_2_10m
  Result object 11: Sentinel_2_10m_2016_12_01_14_45_03_2916
  Result object 12: NM_CNTRS_2016_12_02_00_59_02_4359
  Result object 13: COWI

[Bang Pham Huu]

what causes it because you already have a collection with same name in rasql, so instead of generating random name when import with WCST_import, it will use the import coverage id and add the prefix timestamp to avoid conflict.

[Bang Pham Huu]

please see ​http://rasdaman.org/ticket/1055

[Dimitar Misev]

Yes I was guessing that's what happens, the question is more: what causes to have that collection already in rasdaman, as the user only uses wcst_import and Delete WCS Coverage.
See #1450

My only guess is on Delete Coverage the petascope coverage is deleted but the rasdaman collection is not.

[Bang Pham Huu]

Replying to dmisev:

Yes I was guessing that's what happens, the question is more: what causes to have that collection already in rasdaman, as the user only uses wcst_import and Delete WCS Coverage.
See #1450

My only guess is on Delete Coverage the petascope coverage is deleted but the rasdaman collection is not.

I never seen when delete coverage in Petascope then the collection is not deleted in rasql. The only case which lead to conflict is when one remove petascopedb (e.g: dropdb petascopedb) and leave the rasql db with existing collection. Then when importing a coverage which id is as same as collection, the problem will appear.