[
https://issues.apache.org/jira/browse/KAFKA-10777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mickael Maison resolved KAFKA-10777.
------------------------------------
Resolution: Fixed
> Add additional configuration to control MirrorMaker 2 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: Major
> Labels: mirror, mirror-maker, mirrormaker
> Fix For: 3.1.0
>
>
> 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.
>
> Way to solve this is under-discussion in
> [KIP-690|https://cwiki.apache.org/confluence/display/KAFKA/KIP-690%3A+Add+additional+configuration+to+control+MirrorMaker+2+internal+topics+naming+convention]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
