#83 closed defect (fixed)
Petascope caches metadata for WCS coverages after they have been deleted
Reported by: | Owned by: | Dimitar Misev | |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | petascope | Version: | |
Keywords: | Cc: | ||
Complexity: | Medium |
Description
If metadata for a coverage is updated in the Petascope database WCS requests made on the server do not reflect this until Tomcat is restarted.
If a coverage is deleted Petascope detects this but if a new coverage is created with the same name the cached metadata for the old coverage is used until a restart.
Change History (2)
comment:1 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 by , 12 years ago
jDU8aS <a href="http://tvfumhtmxwhc.com/">tvfumhtmxwhc</a>, [url=http://kkrflwogbrrj.com/]kkrflwogbrrj[/url], [link=http://mftpfuozkupa.com/]mftpfuozkupa[/link], http://vvlfrvjauecl.com/
Note:
See TracTickets
for help on using tickets.
A patch has been submitted: the metadata cache is cleared at the beginning of every request now.