If all of the syncs of data always be filtered, but checkpoint commit ts always doesn't update the new one.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 291
- Forks
- 131
- Avg merge
- 5m
- Merged PRs (30d)
- 2
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
-
What did you do?
If possible, provide a recipe for reproducing the error. -
What did you expect to see?
Even though all of the syncs of data has been filtered, the checkpoint commit ts should update all the time. -
What did you see instead?
-
Please provide the relate downstream type and version of drainer.
(rundrainer -Vin terminal to get drainer's version)
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 by reproducing the checkpoint behavior with a drainer, checking the version with drainer -V, and using a case where every data sync is filtered. Trace the checkpoint commit timestamp handling and verify that the timestamp advances even when no data is synchronized; the issue does not name a file or test to begin with.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- data-engineering, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100