This version requires the 1.0.0
kafka-clients or higher.
The 1.1.x client is supported, with version 2.1.5, but you will need to override dependencies as described in ???. The 1.1.x client will be supported natively in version 2.2.
JsonSerializer now add type information in
Headers, allowing the converter and
JsonDeserializer to create specific types on reception, based on the message itself rather than a fixed configured type.
See Section 4.1.5, “Serialization/Deserialization and Message Conversion” for more information.
Container Error handlers are now provided for both record and batch listeners that treat any exceptions thrown by the listener as fatal; they stop the container. See Section 4.1.8, “Handling Exceptions” for more information.
The listener containers now have
resume() methods (since version 2.1.3).
See Section 4.1.4, “Pausing/Resuming Listener Containers” for more information.
Starting with version 2.1.3, stateful retry can be configured; see the section called “Stateful Retry” for more information.
Starting with version 2.1.1, it is now possible to set the
client.id prefix on
Previously, to customize the client id, you would need a separate consumer factory (and container factory) per listener.
The prefix is suffixed with
-n to provide unique client ids when using concurrency.
By default, logging of topic offset commits is performed with the DEBUG logging level.
Starting with version 2.1.2, there is a new property in
commitLogLevel which allows you to specify the log level for these messages.
See the section called “KafkaMessageListenerContainer” for more information.
Starting with version 2.1.3, one of the
@KafkaHandler s on a class-level
@KafkaListener can be designated as the default.
See the section called “@KafkaListener on a Class” for more information.
Starting with version 2.1.3, a subclass of
KafkaTemplate is provided to support request/reply semantics.
See the section called “ReplyingKafkaTemplate” for more information.
version 2.1.3 introduced the
ChainedKafkaTransactionManager see the section called “ChainedKafkaTransactionManager” for more information.
The Spring for Apache Kafka project now requires Spring Framework 5.0 and Java 8.
You can now annotate
@KafkaListener methods (and classes, and
@KafkaHandler methods) with
If the method returns a result, it is forwarded to the specified topic.
See the section called “Forwarding Listener Results using @SendTo” for more information.
Message listeners can now be aware of the
See the section called “Message Listeners” for more information.
Rebalance listeners can now access the
Consumer object during rebalance notifications.
See the section called “Rebalance Listeners” for more information.
The 0.11.0.0 client library added support for transactions; the
KafkaTransactionManager and other support for transactions has been added.
See the section called “Transactions” for more information.
The 0.11.0.0 client library added support for message headers; these can now be mapped to/from
See Section 4.1.6, “Message Headers” for more information.
The 0.11.0.0 client library provides an
AdminClient which can be used to create topics.
KafkaAdmin uses this client to automatically add topics defined as
KafkaTemplate now supports API to add records with timestamps.
KafkaHeaders have been introduced regarding
KafkaMatchers.hasTimestamp() testing utilities have been added.
See the section called “KafkaTemplate”, the section called “@KafkaListener Annotation” and Section 4.3, “Testing Applications” for more details.
You can now configure a
KafkaListenerErrorHandler to handle exceptions.
See Section 4.1.8, “Handling Exceptions” for more information.
By default, the
id property is now used as the
group.id property, overriding the property configured in the consumer factory (if present).
Further, you can explicitly configure the
groupId on the annotation.
Previously, you would have needed a separate container factory (and consumer factory) to use different
group.id s for listeners.
To restore the previous behavior of using the factory configured
group.id, set the
idIsGroup property on the annotation to
For convenience a test class level
@EmbeddedKafka annotation is provided with the purpose to register
KafkaEmbedded as a bean.
See Section 4.3, “Testing Applications” for more information.
Support for configuring Kerberos is now provided. See Section 4.1.9, “Kerberos” for more information.
Listeners can be configured to receive the entire batch of messages returned by the
consumer.poll() operation, rather than one at a time.
When explicitly assigning partitions, you can now configure the initial offset relative to the current position for the consumer group, rather than absolute or relative to the current end.
You can now seek the position of each topic/partition. This can be used to set the initial position during initialization when group management is in use and Kafka assigns the partitions. You can also seek when an idle container is detected, or at any arbitrary point in your application’s execution. See the section called “Seeking to a Specific Offset” for more information.