-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ImageMosaic plugin layer if deleted, deletes whole database #327
Comments
@aaime can we do a time boxed investigation of this? |
Right now I'm a "bit" under pressure (a few ongoing tickets plus preparing a brand new 8 hours training for next week...). Anyone else that could have a look? |
There's no particular urgency, although it looks quite severe. |
Idea: switch to remote only table, maybe add parameter to control removing database too? But it requires a GeoTools StructuredGridCoverageReader API change. |
No problems on our side to update the api calls actually. |
Updated my comment, I meant at the GeoTools level. |
No problem either, we will include the new geotools on the package. |
@nmco this issue isn't connected to any project, but I think it is worth the effort given its severity (not only for GeoNode). |
JIRA issue for reference here |
Accordingly to this methos here it looks like a
drop
call to theImageMosaic
store will end up dropping the whole DB.E.g.: a rest call like this
http://localhost:8080/geoserver/rest/workspaces/geonode/coveragestores/optimized.xml?purge=all&recurse=true
will force the plugin toDROP
the whole DB defined into thedatastore.properties
fileThis might be a big issue whenever we are going to use the same DB to store more than one
dataset
. In this specific case we will end up dropping all the data withing a single rest call.The text was updated successfully, but these errors were encountered: