[
https://issues.apache.org/jira/browse/KAFKA-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16836058#comment-16836058
]
Ryanne Dolan commented on KAFKA-7500:
-------------------------------------
[~cloudfrog], glad you are taking a look. I'm looking forward to hearing about
your experience.
> Is this expected to work with kafka 1.1.1 clusters?
Yes, I believe it will work with 0.11.0.0 or higher, but maybe you can test it
to verify :)
> will prefix remote topic names ... be configurable?
Yes, you can implement your own ReplicationPolicy to define remote topics
however you like:
{code:java}
replication.policy.class = my.SuffixReplicationPolicy
{code}
Also, MM2 doesn't care how existing source topics are named. If your topics are
prefixed with their local DC (a common pattern), you can leave them as-is
without breaking anything. By default you'd get topics like "dc1.topic1-dc1",
so you might consider implementing a ReplicationPolicy that strips the suffix
during replication so you get just "dc1.topic1".
Ryanne
> 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)
