spring-kafka
spring-kafka copied to clipboard
Provides Familiar Spring Abstractions for Apache Kafka
**Affects Version(s): 2.3.6.RELASE** 🎁 Enhancement Scenario (using transactions and non batch listener) - (point 1-4 in attached log in the bottom): 1. Producer (clientId=producer-12) is created as there is partition...
Fixes: https://github.com/spring-projects/spring-kafka/issues/3396 This pull request updates the documentation to reflect the support for class-level @KafkaListener annotations in the retry topic configuration, available since version 3.2. It corrects the outdated statement...
**In what version(s) of Spring for Apache Kafka are you seeing this issue?** 3.2.2 springboot 3.3.2 **Describe the bug** consumer.auto-commit-interval does not work **To Reproduce** application.yaml ` spring: application: name:...
Containers are not restricted from starting after ConcurrentContainer stopped or restarted. These changes would fix this issue.
**Expected Behavior** Response messages in addition to the `kafka_correlationId` Header should have the same keys as their corresponding request messages when constructing the Request-Reply semantics on top of `ReplyingKafkaTemplate` and...
This [chapter](https://docs.spring.io/spring-kafka/reference/retrytopic/how-the-pattern-works.html) says: > At this time this functionality doesn’t support class level `@KafkaListener` annotations. Which apparently is not true any more according to the info in some [next chapter](https://docs.spring.io/spring-kafka/reference/retrytopic/retry-config.html):...
Hi, while working with ConcurrentKafkaListenerContainerFactory and kafka interceptors we encountered a problem that with bean post processor setting an interceptor there is no possibility to check if there is any...
**In what version(s) of Spring for Apache Kafka are you seeing this issue?** 3.3 **Describe the bug** 1) Start the `ConcurrentMessageListenerContainer` with concurrency 2. 2) Obtain one of the `KafkaMessageListenerContainer`...
**Version** 3.2.2 **Description** `List convertedHeaders = new ArrayList();` ... `addToRawHeaders(rawHeaders, convertedHeaders, natives, raws, conversionFailures);` ... `if (this.headerMapper != null && record.headers() != null) {` `Map converted = new HashMap();` `this.headerMapper.toHeaders(record.headers(),...
Looks like different partitions are registered for same `ConsumerSeekCallback` when we have a multi-`@KafkaListener` scenario. See `AbstractConsumerSeekAwareTests` and its TODO. when we have different groups and `concurrency`, different listener container...