Hey Madhan, The easiest way to get rid of aliases in the topic names is to add the following to your config:
replication.policy.separator= source.cluster.alias= target.cluster.alias= On Thu, Apr 22, 2021 at 11:40 PM Dhanikachalam, Madhan (CORP) <madhan.dhanikacha...@adp.com.invalid> wrote: > I am testing MM2. I got the connector working but it is creating topics in > the downstream cluster like this mm-poc-src.grp1-top1 which is the > alias.<topicname>. How can I create the downstream topic to be the exact > name as the source? > > > > Also, do you provide commercial support for open source kafka? Or direct > me to any firms that offer Open source kafka support? > > > > I am also testing kafkadrop. Looking for an open source tool that has the > feature to browse messages and also maintain history information. Do you > recommend any? Please let me know. Thanks. > > > > > > > > > > [image: /Users/wardg/Documents/April 2019 Email Signature/ADP_Email > signature_032...@2x.png] > > Thanks > > Madhan Dhanikachalam > > *GETS Transformers* > > > > To open tickets to my team follow below links > > *MFT:* > http://servicecatalog:8080/usm/wpf?Node=icguinode.catalogitemdetails&Args=10933&ObjectID=10933&NspPath > = > > *MQ:* > http://servicecatalog:8080/usm/wpf?Node=icguinode.catalogitemdetails&Args=10688&ObjectID=10688&NspPath > = > > > > > > > ------------------------------ > This message and any attachments are intended only for the use of the > addressee and may contain information that is privileged and confidential. > If the reader of the message is not the intended recipient or an authorized > representative of the intended recipient, you are hereby notified that any > dissemination of this communication is strictly prohibited. If you have > received this communication in error, notify the sender immediately by > return email and delete the message and any attachments from your system. >
