We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is your feature request related to a problem? Please describe.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-932%3A+Queues+for+Kafka#KIP932:QueuesforKafka-Fetchingandacknowledgingrecords is adding a ShareConsumer API to the Kafka Client. This project already has Closable* wrappers around Admin, Consumer and Producer which give #close a sensible close timeout.
It may wish to add a similar wrapper around ShareConsumer in order to keep the symmetry. It will support the test cases around share consumers.
ShareConsumer
KIP-932 is still partly implemented in 3.9, but it is marked unstable.
Describe the solution you'd like A clear and concise description of what you want to happen.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-932%3A+Queues+for+Kafka#KIP932:QueuesforKafka-Fetchingandacknowledgingrecords is adding a ShareConsumer API to the Kafka Client. This project already has Closable* wrappers around Admin, Consumer and Producer which give #close a sensible close timeout.
It may wish to add a similar wrapper around
ShareConsumer
in order to keep the symmetry. It will support the test cases around share consumers.KIP-932 is still partly implemented in 3.9, but it is marked unstable.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: