Skip to content

Support for KIP-932 Queues for Kafka #3875

New issue

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

Open
ivamly opened this issue Apr 28, 2025 · 1 comment
Open

Support for KIP-932 Queues for Kafka #3875

ivamly opened this issue Apr 28, 2025 · 1 comment

Comments

@ivamly
Copy link
Contributor

ivamly commented Apr 28, 2025

Hi!

With the release of Kafka 4.0, I would like to know about plans to support KIP-932: Queues for Kafka, which is currently in early access. Are there any plans to support or start development on this feature, or will it start as we get closer to stable status? Thanks!

@sobychacko
Copy link
Contributor

Hi, yes, we have it on the roadmap. After some internal planning around its design, we will most likely provide some early versions in the upcoming milestones.

sobychacko added a commit to sobychacko/spring-kafka that referenced this issue May 23, 2025
- Preliminary set of changes to support Kafka queueus introduced via KIP-932 (Kafka Queue)
  for early access in Apache Kafka 4.0.0.
  See: https://cwiki.apache.org/confluence/display/KAFKA/KIP-932%3A+Queues+for+Kafka

- Add ShareConsumerFactory interface and DefaultShareConsumerFactory implementation as the
  initial building blocks for supporting Kafka Queues (KIP-932) in Spring for Apache Kafka 4.0.x.
  This factory and the implementation provide a flexible API for creating share consumers,
  and are designed as the foundation for further queue integration.

- Tests to verify the share consumer behavior

Related to spring-projects#3875

spring-projects#3875

Signed-off-by: Soby Chacko <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants