You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Ryanne Dolan (JIRA)" <ji...@apache.org> on 2019/03/13 19:42:00 UTC

[jira] [Commented] (KAFKA-6340) Support of transactions in KafkaConnect

    [ https://issues.apache.org/jira/browse/KAFKA-6340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792052#comment-16792052 ] 

Ryanne Dolan commented on KAFKA-6340:
-------------------------------------

Do we think we need a KIP for this change? For the most part it's an internal change, but we may want to expose a configuration property to enable/disable EOS like Streams does.

> Support of transactions in KafkaConnect
> ---------------------------------------
>
>                 Key: KAFKA-6340
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6340
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>            Reporter: Oleg Kuznetsov
>            Priority: Major
>
> Now KafkaConnect source connectors commit source offset in periodic task.
> Proposed approach is to produce data record batch and the config update records (related to the batch) within Kafka transaction, that would prevent publishing duplicate records on connector restart.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)