MeltanoLabs / MeltanoLabs/tap-postgres
Stop swallowing json parse errors during log based
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Why are we swallowing this?
Originally posted by @visch in https://github.com/MeltanoLabs/tap-postgres/pull/249#discussion_r1357357253
Contributor guide
No contributing guide indexed for this repository
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 discussion in pull request #249 and trace the log-based JSON parsing path it refers to; the issue does not name a file, test, or entry point. Determine which parse errors are currently swallowed and define completion as preserving or reporting those errors without breaking the surrounding PostgreSQL tap flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100