Skip to content
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

Open
afabiani opened this issue Feb 28, 2022 · 10 comments
Open

ImageMosaic plugin layer if deleted, deletes whole database #327

afabiani opened this issue Feb 28, 2022 · 10 comments

Comments

@afabiani
Copy link
Member

Accordingly to this methos here it looks like a drop call to the ImageMosaic 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 to DROP the whole DB defined into the datastore.properties file

This 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.

@giohappy
Copy link

giohappy commented Mar 3, 2022

@aaime can we do a time boxed investigation of this?

@aaime
Copy link
Member

aaime commented Mar 3, 2022

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?

@giohappy
Copy link

giohappy commented Mar 3, 2022

There's no particular urgency, although it looks quite severe.

@aaime
Copy link
Member

aaime commented Mar 11, 2022

Idea: switch to remote only table, maybe add parameter to control removing database too? But it requires a GeoTools StructuredGridCoverageReader API change.

@afabiani
Copy link
Member Author

No problems on our side to update the api calls actually.

@aaime
Copy link
Member

aaime commented Mar 11, 2022

Updated my comment, I meant at the GeoTools level.

@giohappy
Copy link

@afabiani?

@afabiani
Copy link
Member Author

No problem either, we will include the new geotools on the package.

@giohappy
Copy link

@nmco this issue isn't connected to any project, but I think it is worth the effort given its severity (not only for GeoNode).
Do you think we should proceed with the fix?

@afabiani
Copy link
Member Author

JIRA issue for reference here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants