THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- When users upgrade an existing MM2 cluster they don’t need to change any of their current configuration If they are using the default
replication.policy.separator
as this proposal maintains the default behaviour for MM2 with the default configs. - If users upgrade an existing MM2 to 3.1.x, 3.2.x, 3.3.x, 3.4.x, 3.5.x and they are using customised
replication.policy.separator
they need to provide a new version of `DefaulReplicationPolicy
` thatoverride `ReplicationPolicy.offsetSyncsTopic`and `ReplicationPolicy.checkpointsTopic` methods to use old topics if they still want to use the old internal topics . Related JIRA to this is discussed in KAFKA-15102.
Rejected Alternatives
1- Add new interface for internal policies, the reason to reject is to minimise the number of MM2 customised classes
...