[ENHANCEMENT]: Add seq checkpoints to continuous feeds
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
Research direction
No files or tests are named. Start by tracing the continuous-feed and filtered-feed handling, then inspect how sequence values are currently emitted and how clients can checkpoint them. Done means the feed provides a reliable tail sequence sentinel during periods without winning revisions, including filtered feeds, with coverage for the new behavior.
Written by the indexing model from the issue text.
Description
Provide a brief overview of what the new feature is all about
When doing a continuous feed it's not possible to get sequences that did not create winning revisions which makes it impossible to follow the feeds update to date sequence relative to create a user side checkpoint.
This is especially important on filtered feeds. Since a row may not arrive for several minutes or hours and the client has no way to create checkpoints during this time. The workaround of using timeout=N is not as nice.
Tell us how the new feature should work. Be specific
Add an option to output some kind of sentinel, e.g. { seq, changes: [], id: null } that a client can use to save an up to date checkpoint at the tail of the db feed.
Not required. Suggest how to implement the addition or change
No response
Additional Context
No response
- Dominant language
- Erlang
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 1d 23m
- Merged PRs (30d)
- 30
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from apache/couchdb
-
Fix: Warning: 'catch ...' is deprecated; please use 'try ... catch ... end' insteadPossibly taken @devx-arjun claimed this 4 days ago. Openbeginner-friendly build chore patches-welcome
Difficulty 4/5 3-5 days Newbie friendliness 45/100
apache/couchdb#6144 · 4 comments ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
apache/couchdb#6132 · 3 comments ·
Maintainers usually reply within 1 day
-
enhancement needs-triage
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
apache/couchdb#6109 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
factory-active factory-automatic task-bug-reproduction-success task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
vercel/ai#22796 · 2 comments ·
Maintainers usually reply within 1 day
-
good first issue no-box
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
peasant-labs/peasant#596 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hatchet-dev/hatchet#5179 ·
Maintainers usually reply within 1 day