Spring/spring-kafka
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add ChainedKafkaTransactionManager

Browse Source 
Enable transaction synchronization without the need for user code to
send the offset(s) to the transaction.
This commit is contained in:
Gary Russell
2018-02-16 12:57:05 -05:00
committed by Artem Bilan
parent b25e1441bd
commit 60f92c87fc
7 changed files with 137 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
src/reference/asciidoc/kafka.adoc
View File

@@ -280,7 +280,7 @@ If the listener throws an exception, the transaction is rolled back and the cons
If you need to synchronize a Kafka transaction with some other transaction; simply configure the listener container with the appropriate transaction manager (one that supports synchronization, such as the `DataSourceTransactionManager`).
Any operations performed on a **transactional** `KafkaTemplate` from the listener will participate in a single transaction.
The Kafka transaction will be committed (or rolled back) immediately after the controlling transaction.
Before exiting the listener, you should invoke one of the template's `sendOffsetsToTransaction` methods.
Before exiting the listener, you should invoke one of the template's `sendOffsetsToTransaction` methods (unless you use a <<chained-transaction-manager, `ChainedKafkaTransactionManager` - see below>>).
For convenience, the listener container binds its consumer group id to the thread so, generally, you can use the first method:
[source, java]
@@ -317,6 +317,15 @@ NOTE: The offset to be committed is one greater than the offset of the record(s)
IMPORTANT: This should only be called when using transaction synchronization.
When a listener container is configured to use a `KafkaTransactionManager`, it will take care of sending the offsets to the transaction.
[[chained-transaction-manager]]
====== ChainedKafkaTransactionManager
The `ChainedKafkaTransactionManager` was introduced in _version 2.1.3_.
This is a subclass of `ChainedTransactionManager` that can have exactly one `KafkaTransactionManager`.
Since it is a `KafkaAwareTransactionManager`, the container can send the offsets to the transaction in the same way as when the container is configured with a simple `KafkaTransactionManager`.
This provides another mechanism for synchronizing transactions without having to send the offsets to the transaction in the listener code.
Chain your transaction managers in the desired order and provide the `ChainedTransactionManager` in the `ContainerProperties`.
====== KafkaTemplate Local Transactions
You can use the `KafkaTemplate` to execute a series of operations within a local transaction.

4
src/reference/asciidoc/whats-new.adoc
View File

@@ -42,6 +42,10 @@ See <<class-level-kafkalistener>> for more information.
Starting with _version 2.1.3_, a subclass of `KafkaTemplate` is provided to support request/reply semantics.
See <<replying-template>> for more information.
==== ChainedKafkaTransactionManager
_version 2.1.3_ introduced the `ChainedKafkaTransactionManager` see <<chained-transaction-manager>> for more information.
==== Migration Guide from 2.0
https://github.com/spring-projects/spring-kafka/wiki/Spring-for-Apache-Kafka-2.0-to-2.1-Migration-Guide[2.0 to 2.1 Migration].