[
https://issues.apache.org/jira/browse/KAFKA-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170425#comment-17170425
]
Ryanne Dolan commented on KAFKA-10339:
--------------------------------------
Yeah, I guess it would be possible to switch from MirrorSourceConnector to
MirrorSinkConnector in the connect-mirror-maker "driver", but external tooling
would notice (e.g. JMX metrics would change), so we'd need to put that behind a
flag or something so users could opt-in to the SinkConnector in order to get
EOS. But even without changing the "driver', an EOS MirrorSinkConnector would
be very useful to many organizations that run MM2 on existing Connect clusters.
> 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)
