confluentinc / confluentinc/ksql
Command topic producer should use EXACTLY ONCE.
Open
enhancement
- Dominant language
- Java
- Stars
- 315
- Forks
- 1k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 36
Description
Currently, by default exactly once is not set for the producer for the command topic. This can result in corner cases where we have duplicate commands in the command topic. We should set the producer for the command topic to use exactly once.
Contributor guide
Research direction
Start by tracing the producer used for the command topic and inspect how its delivery settings are configured. Confirm the intended exactly-once setting and add or update coverage for duplicate-command behavior; done means command-topic production uses exactly once by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka
- Domain
- stream-processing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100