[
https://issues.apache.org/jira/browse/KAFKA-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170377#comment-17170377
]
Ryanne Dolan commented on KAFKA-10339:
--------------------------------------
[~yangguo1220] this is awesome, thanks! My team has looked into this multiple
times, and we came to the same conclusion around WorkerSourceTask requiring a
lot of changes to support transactions. I believe it would be easier to start
from scratch with a new SourceWorker than to adapt it to support transactions,
and we'd probably need to deprecate a number of APIs in the process. I wouldn't
rule it out, but it would be difficult.
Love how your KIP "kills two birds with one stone" -- we get a
MirrorSinkConnector _and_ EOS.
> MirrorMaker2 Exactly-once Semantics
> -----------------------------------
>
> Key: KAFKA-10339
> URL: https://issues.apache.org/jira/browse/KAFKA-10339
> Project: Kafka
> Issue Type: New Feature
> Components: KafkaConnect
> Reporter: Ning Zhang
> Assignee: Ning Zhang
> Priority: Major
> Labels: needs-kip
>
> MirrorMaker2 is currently implemented on Kafka Connect Framework, more
> specifically the Source Connector / Task, which do not provide exactly-once
> semantics (EOS) out-of-the-box, as discussed in
> https://github.com/confluentinc/kafka-connect-jdbc/issues/461,
> https://github.com/apache/kafka/pull/5553,
> https://issues.apache.org/jira/browse/KAFKA-6080 and
> https://issues.apache.org/jira/browse/KAFKA-3821. Therefore MirrorMaker2
> currently does not provide EOS.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
