Opened 7 years ago

Last modified 7 years ago

#1643 closed defect

Petascope migration should continue when cannot migrate error coverages — at Initial Version

Reported by: Bang Pham Huu Owned by: Bang Pham Huu
Priority: major Milestone: 9.5
Component: petascope Version: development
Keywords: Cc: Dimitar Misev, Vlad Merticariu
Complexity: Medium

Description

Example case from PML when coverage was imported with rasimport
in petascopedb9.4 table ps_rasdaman_collection, the base_type is only collectionName, with coverage imported by wcst_import it should be collectionName:collectionType.

Then this one will throw an exception and migration process will stop, it should continue with other coverages and ignore this error coverage.

Change History (0)

Note: See TracTickets for help on using tickets.