Opened 8 years ago
Closed 8 years ago
#1306 closed defect (fixed)
DeleteCoverage should remove the relevant layer from WMS
| Reported by: | Dimitar Misev | Owned by: | Bang Pham Huu |
|---|---|---|---|
| Priority: | minor | Milestone: | 9.3 |
| Component: | petascope | Version: | development |
| Keywords: | Cc: | ||
| Complexity: | Medium |
Description
right now it stays in the WMS tables, and if the same coverage is ingested again, the old OID of the deleted coverage is still used for WMS queries, which fails.
To reproduce:
- ingest coverage A and insert in WMS as well
- delete A
- ingest A again
- try some rasql style
Change History (3)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
| Milestone: | 9.2 → 9.3 |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
I think I can do this, so will assign to me.
comment:3 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
http://rasdaman.org/wiki/WMSGuide#Dataingestionremoval There is a DeleteLayer operation that should help for the moment.
For the future I agree, we need to remove it as well and once nD support is available in WMS we should not make any diferences between coverages and layers.