Number of log files under edit-drafts folder is over growing
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
What inspired the request?
Under /usr/local/payara5/glassfish/domains/domain1/logs/edit-drafts folder, the number of files is overgrowing (around 10K).
What existing behavior do you want changed?
- It will be helpful if some information is provided under https://guides.dataverse.org/en/6.0/admin/monitoring.html#edit-draft-versions-logging for managing these files.
Do not know what are the scenarios or there are any APIs to use/retrieve the information logged by these files.
Since each file adds on to the change history of a dataset, deleting them based on date/time may not be correct.
-
Instead of creating one file for each change, one edit-draft file per dataset doi can be maintained to reduce the number of files.
-
It will be helpful if there is an configuration option to turn off this feature if people don't want to use it.
For e.g.:
curl -X PUT -d 'true' http://localhost:8080/api/admin/settings/:EditDraftFilesEnabled
Any brand new behavior do you want to add to Dataverse?
Any open or closed issues related to this feature request?
related google group post: https://groups.google.com/g/dataverse-community/c/eCii8K3LYJo/m/JT6JiCPEHQAJ
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 with the edit-draft versions logging section in the monitoring guide and review related issues 5145 and 1002. Determine the supported scenarios and APIs for these files, then define the required behavior for retention, per-dataset storage, and disabling the feature; completion should include agreed implementation scope and corresponding documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100