Opened 12 months ago
Closed 12 months ago
#2724 closed enhancement (fixed)
FIX - if a coverage's set type doesn't exist in rasdaman, petascope should still start
| Reported by: | Bang Pham Huu | Owned by: | Bang Pham Huu |
|---|---|---|---|
| Priority: | major | Milestone: | 10.2 |
| Component: | petascope | Version: | 10.2 |
| Keywords: | Cc: | Dimitar Misev | |
| Complexity: | Medium |
Description
Petascope should still start even if a coverage's set type doesn't exist in rasdaman. It should not show this coverage in GetCapabilities and should log in petascope.log, for example:
Set type 'test_mr_TO_BE_DELETED_Set' does not exist in rasdaman, but is required for coverage 'test_mr_TO_BE_DELETED'. Hint: create the missing set type, or delete the coverage in petascope with a DeleteCoverage request.
Note:
See TracTickets
for help on using tickets.
