Skip to content
This repository has been archived by the owner on Jan 9, 2020. It is now read-only.

Removing S3 folder does not delete dataset that references it #81

Open
kotfic opened this issue Aug 20, 2015 · 2 comments
Open

Removing S3 folder does not delete dataset that references it #81

kotfic opened this issue Aug 20, 2015 · 2 comments
Milestone

Comments

@kotfic
Copy link
Contributor

kotfic commented Aug 20, 2015

Datasets reference items in the s3 folder, removing the s3 folder does not cascade a delete of datasets that reference it.

@mgrauer
Copy link
Contributor

mgrauer commented Aug 20, 2015

I don't fully understand what is desired here. Let's say we have a dataset that is derived from an item in S3 but no longer relies on the original item. Would you want this dataset deleted?

@kotfic
Copy link
Contributor Author

kotfic commented Aug 20, 2015

No I don't think we would want to delete it in that case,

The scenario I was thinking of is this:

  • Add an s3 dataset through the minerva interface
    • this creates an s3 assetstore
    • this creates a folder under the User Name > minerva > s3 folder where the item data is imported based on the s3 bucket name (e.g. nasanex) and the prefix (e.g., NEX-DCP30)
    • this creates an item under User Name > minerva > datasets (e.g. NEX Test)
  • Someone goes into the backend in girder and removes the User Name > minerva > s3 > nasanex > NEX-DCP30 folder.
  • Now the NEX Test Item has metadata that refers to a folder that no longer exists.
  • On the front end if you go to browse NEX Test the widget shows an empty folder.

Ideally we would delete dataset (or "data source") items on s3 folder removal.

@aashish24 aashish24 added this to the Release 0.2.0 milestone Feb 16, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants