S3/API duplicate upload and/or force-replace leaves file behind in files.dir/temp
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Not much to go on in the logs, but three times now a user has attempted to force-replace a duplicate tabular datafile:
jsonData: {"forceReplace":true}
REPLACE!
we're back.....
yes, has error
which leaves a CSV behind in files.dir/temp. We're running Dataverse 5.3 with one S3 bucket; I may try to replicate this on a test server to get a better handle on where clean-up isn't happening.
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 reproducing the duplicate tabular-data upload through the S3/API path with forceReplace enabled, then inspect cleanup involving files.dir/temp. The issue provides no source file or test entry point, so trace the failed replacement flow and identify where the CSV remains. Done means the failure is reproducible and temporary files are removed after duplicate or force-replace handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- backend, cloud, data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100