singer-io / singer-io/tap-github
`pull_requests` table contains many duplicates since upgrade to v2
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 76
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Description
Hi, we have upgraded our Github integration to v2 on Stitch one week ago. Since then it seems the pull_requests table contains many duplicates of some pull requests. This is weird since the primary key is indeed id
Could please you help us on this?
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 by reproducing the v2 extraction against the GitHub pull request data and inspect the duplicate records in the pull_requests table, using the reported primary key id as the comparison point. Done means the cause of the duplicate records is identified and a repeat extraction no longer produces duplicates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100