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

Posted to jira@kafka.apache.org by "Dan Casey (JIRA)" <ji...@apache.org> on 2019/05/09 02:32:00 UTC

[jira] [Commented] (KAFKA-7500) MirrorMaker 2.0 (KIP-382)

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

Dan Casey commented on KAFKA-7500:
----------------------------------

I'm excited to test this as well.  We've been fighting with duplicates for a long time, and wasting a lot of resources dealing with duplicate detection and remediation.

I have a few questions about the initial release.
 # Is this expected to work with kafka 1.1.1 clusters?  This is currently the max version we can upgrade to without breaking support for vertica integration.
 # KIP-382 mentions that you will prefix remote topic names to avoid replication loops.  Would this be configurable?  I am already using a similar approach by adding the local datacenter as a suffix to my topics although it requires the producer to be datacenter aware, and additionally prevents the ability to create aggregate topics without help of app.  Would be great to see options to transform destination topic names.

> MirrorMaker 2.0 (KIP-382)
> -------------------------
>
>                 Key: KAFKA-7500
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7500
>             Project: Kafka
>          Issue Type: New Feature
>          Components: KafkaConnect, mirrormaker
>            Reporter: Ryanne Dolan
>            Assignee: Ryanne Dolan
>            Priority: Minor
>
> Implement a drop-in replacement for MirrorMaker leveraging the Connect framework.
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-382%3A+MirrorMaker+2.0



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