[
https://issues.apache.org/jira/browse/CAMEL-21791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959670#comment-17959670
]
Claus Ibsen commented on CAMEL-21791:
-------------------------------------
I think this should be done in multiple steps.
At first is to make existing transaction code in camel-kafka easier to use. As
today you have to do like in
KafkaTransactionIT by setting additional-properties.
Instead we should have camel specific options
- transacted (boolean)
- transacted-prefix-id (string)
That indirectly then configures those special kafka options ala
additional-properties
Anything else lets wait as this is harder to do, in case of JTA / spring etc.
> camel-kafka - Make kafka transactions more easier to use
> --------------------------------------------------------
>
> Key: CAMEL-21791
> URL: https://issues.apache.org/jira/browse/CAMEL-21791
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
> Reporter: Claus Ibsen
> Assignee: Claudio Miranda
> Priority: Major
> Fix For: 4.x
>
>
> We should make it possible to use by setting transacted=true, and allow
> optional transaction.id prefix (need to generate uid). See for example how
> spring-kafka does it.
> Also it may be that we need to have support for invoking being/commit/abort
> transaction methods, and if we can integrate this with spring-transaction /
> jta via Camel transacted EIP.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
