Add admin-only destroy datafile command and the api that could be used on *published* files
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
(just like the "destroy dataset" equivalents).
As we are starting to seriously enforce storage quotas and limits on the number of files in datasets, it will become a frequent real life use case, where users will need to have to permanently delete files from published versions. To stay under the quota and/or re-package their data in a more manageable number of files.
To avoid having to do this via direct database/storage hacks, we need to add a real API for this.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing “destroy dataset” command and API equivalents mentioned in the issue, then trace how they handle administration and published data. Define the corresponding datafile command and API behavior, including permanent deletion from published versions; done means authorized users can use it without direct database or storage intervention.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100