Native API fails to update data file in published dataset
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
When attempting to edit the metadata of a file in a published dataset via API, the POST request returns the following error:
{"status":"ERROR","message":"Filename already exists at xxxx.jpg"}
Identical requests that pass file IDs on draft datasets are successfully edited. The UI supports editing published data files by creating a new draft and version when published.
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 at the Native API endpoint that handles metadata edits for files in published datasets and reproduce the request using a file ID. Compare its published-dataset path with the draft-dataset behavior; done means a published edit follows the UI's draft-and-version flow without the filename-already-exists error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100