On #2, you can provide an implementation of a MirrorMakerMessageHandler that will called for each record - you ensure it's in the classpath and pass the class name to MM using --message.handler.
On Thu, 20 Feb. 2020, 9:49 pm Dean Barlan, <dean.bar...@grab.com.invalid> wrote: > Hi everyone, > > I have a few small questions for you regarding MirrorMaker. > > 1. I know that MirrorMaker 2.0 is only available starting with Kafka > version 2.4. Does that mean that if I was mirroring from cluster A to > cluster B, that both clusters need to be running Kafka 2.4? > > 2. For MirrorMaker 1.0, is there a way to change the name of the mirrored > topic? For testing, I have just one Kafka cluster and was trying to run MM > replicating from a topic to the same cluster but have a different name. > > Thanks, > > -- > *_Grab is hiring. Learn more at _**https://grab.careers > <https://grab.careers/>* > > > By communicating with Grab Inc and/or its > subsidiaries, associate companies and jointly controlled entities (“Grab > Group”), you are deemed to have consented to the processing of your > personal data as set out in the Privacy Notice which can be viewed at > https://grab.com/privacy/ <https://grab.com/privacy/> > > > This email contains > confidential information and is only for the intended recipient(s). If you > are not the intended recipient(s), please do not disseminate, distribute > or > copy this email Please notify Grab Group immediately if you have received > this by mistake and delete this email from your system. Email transmission > cannot be guaranteed to be secure or error-free as any information therein > could be intercepted, corrupted, lost, destroyed, delayed or incomplete, > or > contain viruses. Grab Group do not accept liability for any errors or > omissions in the contents of this email arises as a result of email > transmission. All intellectual property rights in this email and > attachments therein shall remain vested in Grab Group, unless otherwise > provided by law. > >
