Opened 4 years ago
Closed 4 years ago
#2346 closed defect (fixed)
Petascope - stopping rasdaman in the middle of updating a time slice should not persist the time slice to petascopedb
Reported by: | Bang Pham Huu | Owned by: | Bang Pham Huu |
---|---|---|---|
Priority: | major | Milestone: | 10.0 |
Component: | petascope | Version: | 9.8 |
Keywords: | Cc: | Dimitar Misev, Vlad Merticariu | |
Complexity: | Medium |
Description
To reproduce, import 2D time slices to a 3D coverage with this ingredient file. 1 tiff file like: COLOR_CHLORA_2015-02.TIFF
with size: 0:3599,0:1799
{ "config": { "service_url": "http://localhost:8080/rasdaman/ows", "tmp_directory": "/tmp/", "crs_resolver": "http://localhost:8080/def/", "mock": false, "automated": true }, "input": { "coverage_id": "AverageChloroColor2", "paths": [ "COLOR*.TIFF" ] }, "recipe": { "name": "time_series_irregular", "options": { "time_parameter": { "filename": { "regex": "(.*)_(.*)\\.(.*)", "group": "2" }, "datetime_format": "YYYY-MM" }, "time_crs": "http://localhost:8080/def/crs/OGC/0/AnsiDate", "tiling": "ALIGNED [0:3600, 0:1800, 3]" } } }
Then, when it is updating the second tiff file (second time slice). Restart rasdaman with stop_rasdaman.sh && start_rasdaman.sh
.
Petascope still marks this second file as imported (check coefficients of coverage).
It should throw error, as rasdaman was stopped during updating the second time slice.
Note:
See TracTickets
for help on using tickets.