...
Since KIP-690: Add additional configuration to control MirrorMaker 2 internal topics naming convention , the replication.policy.separator
has been used to control the name of internal topics for DefaultReplicationPolicy
, causing backward compatibility issues if users set a customized replication.policy.separator
. This impacted 3.1, 3.2, 3.3, 3.4, 3.5 versions.
Currently, the only way to work around this is either by providing a new version of ReplicationPolicy (which can optionally subclass the DefaultReplicationPolicy class) that overrides the ReplicationPolicy.offsetSyncsTopic and ReplicationPolicy.checkpointsTopic methods to use old topics if users still want to use the old internal topics, or by deleting the old internal topics and letting MM2 set up the new ones.
...