You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Omnia Ibrahim (Jira)" <ji...@apache.org> on 2020/12/03 18:26:00 UTC

[jira] [Updated] (KAFKA-10777) Add additional configuration to control MirrorMaker2 internal topics naming convention

     [ https://issues.apache.org/jira/browse/KAFKA-10777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Omnia Ibrahim updated KAFKA-10777:
----------------------------------
    Summary: Add additional configuration to control MirrorMaker2 internal topics naming convention  (was: Add additional configuration to control MM2 internal topics naming convention)

> Add additional configuration to control MirrorMaker2 internal topics naming convention
> --------------------------------------------------------------------------------------
>
>                 Key: KAFKA-10777
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10777
>             Project: Kafka
>          Issue Type: Improvement
>          Components: mirrormaker
>    Affects Versions: 2.6.0
>            Reporter: Omnia Ibrahim
>            Assignee: Omnia Ibrahim
>            Priority: Minor
>              Labels: mirror, mirror-maker, mirrormaker
>
> MM2 internal topic names (heartbeats, checkpoints and offset-syncs) are hardcoded in the source code which makes it hard to run MM2 with any Kafka Cluster that has rules around topic’s naming convention and doesn’t allow auto-creation for topics.
> In this case developers will need to create these internal topics up-front manually and make sure they do follow the cluster rules and guidance for topic creation, so MM2 should have flexibility to let you override the name of internal topics to follow their cluster topic naming convention. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)