restatedev / restatedev/restate
Kafka subscriptions can be made multiple times for the same source and sink
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4.4k
- Forks
- 207
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 61
Description
It may make sense to have a sense check where if you're registering the source (ie topic) and same sink (ie sevice/method) as an existing subscription, we idempotently accept without making a new one. That is, unless we think theres a use case for having more than one.
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 locating the Kafka subscription registration entry point and tracing how source and sink pairs are stored. Determine whether repeated registration should be idempotent or support multiple subscriptions, then define the expected behavior and tests for duplicate source-and-sink pairs before making a change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kafka, rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100