Support providing watch_id in WatchCreateRequest
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 546
- Forks
- 76
- Avg merge
- 22h 46m
- Merged PRs (30d)
- 13
Description
Recent versions of etcdv3 allow specifying watch_id in WatchCreateRequest, as described here. This would allow attaching multiple watches in parallel. It would be nice if you could tell the client to use this functionality and not always do it sequentially through AttachQueue.
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
Read the WatchCreateRequest definition in proto/rpc.proto, then trace the client's AttachQueue path to understand why watch creation is sequential. Determine how an optional watch_id should enable parallel watch attachment, and verify that multiple watches can be created concurrently without breaking existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, node.js, typescript
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100