confluentinc / confluentinc/parallel-consumer
Missing feature to terminate processing
- Dominant language
- Java
- Stars
- 299
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
I just evaluated this library for use in our product. But sadly, the missing termination feature from within the poll lambda is a show stopper. How come such a trivial and highly useful feature is missing? If I can only fail a record over and over again, there must be a way to stop processing gracefully altogether.
Is this feature coming soon?
And why is the poll lambda relying on exception handling instead of a proper return value? Using exception handling for flow control is very outdated and should not be the norm anymore.
Thanks!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the poll lambda contract and the current exception-based failure path described in the issue. Clarify how processing should terminate gracefully without repeatedly failing a record, then confirm the desired return or control-flow semantics with maintainers before identifying the affected implementation and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100