installations extant prior to v4.8 may still have varchar255 ingestreport
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
As of version 4.7.1 ingestreport.report was created as varchar255: https://github.com/IQSS/dataverse/blob/develop/scripts/database/create/create_v4.7.1.sql#L105
In version 4.8 ingestreport.report was changed to text: https://github.com/IQSS/dataverse/blob/develop/scripts/database/create/create_v4.8.1.sql#L109
However, I don't find any upgrade script in scripts/database/upgrades/ so it's possible that installations which existed prior to v4.8 may be unable to insert the explanation of ingest failure due to: org.postgresql.util.PSQLException: ERROR: value too long for type character varying(255)
Dataverse still catches the failed ingest state, so this is merely an inconvenience to the end user.
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
Compare the ingestreport.report definitions in scripts/database/create/create_v4.7.1.sql and create_v4.8.1.sql, then inspect scripts/database/upgrades/ for the applicable migration conventions. Verify that an installation upgraded from before v4.8 can store an ingest failure explanation longer than 255 characters; done means the existing column is migrated to text without disrupting ingest handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100