files which fail ingest can't be un-ingested, warning can't be dismissed
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
which makes sense as the files weren't ingested, but they continue to have a Big Red Warning that archivists don't like to see. These apparently can't be dismissed without tinkering in the DB. Calling the uningest API endpoint against a problem file returns:
{"status":"ERROR","message":"Cannot uningest non-tabular file."}
Verified on 5.0 release.
To reproduce: head a .csv file for brevity's sake, and remove a random field from a line or two before uploading. Ingest will fail on column count mismatch. Work-around is to delete-and-re-upload, but for sizable datasets with larger files this results in a respectable amount of system churn.
It would be great to be able to dismiss the failed ingest warning.
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
Reproduce the failure by truncating a CSV row, uploading it, and calling the uningest API endpoint; start by tracing how non-tabular failed ingests are handled and how the warning is represented. Done means archivists can dismiss the failed-ingest warning without database tinkering, while valid ingest and uningest behavior remain intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100