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

[BUG] [FEATURE] #7

Open
dvnicolasdh opened this issue Dec 6, 2021 · 1 comment
Open

[BUG] [FEATURE] #7

dvnicolasdh opened this issue Dec 6, 2021 · 1 comment

Comments

@dvnicolasdh
Copy link

dvnicolasdh commented Dec 6, 2021

With a compiled version 2.9.4 of CKAN

and complied version v1.0.0 of ckanext-s3filestore

and configured to store on a Minio version: 2020-09-26T03:44:56Z (same behavior with Minio version: RELEASE.2021-11-24T23-19-33Z)

  • Uploading/Downloading of Dataset Ressources through CKAN does store/retreive in S3 (MinIO).
  • But removal or deletion of a Dataset's Ressource in CKAN doesn't remove that ressource from S3 (MinIO).

Expected behaviour
One could expect deletion mechanism to have the actual ressource deleted from storage, including S3 (MinIO) .

Logs
There are no "errror" messages...

On another ckanext-s3filestore's archived github project's "bug/feature" report/response:

seem to point to "clear_key" definition and usage in the "uploader.py".

Any thought on this ?

@HristijanVilos
Copy link
Member

Yes this is a known issue and could be considered as a feature since CKAN local storage works the same i.e. it does not delete resources from the local file system. We will take this in consideration and implement this feature.

terence-cevo pushed a commit to terence-cevo/ckanext-s3filestore that referenced this issue Jun 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants