[
https://issues.apache.org/jira/browse/KAFKA-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15755909#comment-15755909
]
James Cheng commented on KAFKA-3841:
[~yangguo1220], should we mark this JIRA as "reso
[
https://issues.apache.org/jira/browse/KAFKA-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15330828#comment-15330828
]
James Cheng commented on KAFKA-3841:
More comments here:
https://github.com/gwenshap/
[
https://issues.apache.org/jira/browse/KAFKA-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15330827#comment-15330827
]
James Cheng commented on KAFKA-3841:
We have a similar use case. Mirrormaker has a con
[
https://issues.apache.org/jira/browse/KAFKA-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15330877#comment-15330877
]
Ning Zhang commented on KAFKA-3841:
---
Thanks. This is good to know. As MessageHandler was
We have also something similar, it's real easy to use a message handler, in
our case we check for a bit to determine if we already copied the event,
and change the topic name in dev-mode. You can configure a string to pass
to your messageHandler for each instance.
On Wed, Jun 15, 2016 at 1:38 AM N