THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- When set to requested, MirrorMaker will use the IncrementalAlterConfigs for syncing topic configurations. If it receives an error from an incompatible broker, will use the deprecated AlterConfigs API instead. It will also API instead and log a WARN message that says e.g. "The target cluster <ALIAS> is not compatible with IncrementalAlterConfigs API. Therefore using deprecated AlterConfigs API for syncing topic configurations.".
- When explicitly set to never, MirrorMaker will use the deprecated AlterConfigs API for syncing topic configurations.
- When explicitly set to required, MirrorMaker will use the IncrementalAlterConfigs API for syncing topic configurations. If it receives an error from an incompatible broker, the MirrorMaker will report this to the user and fail the connector. It will log an error that says "The target cluster <ALIAS> is not compatible with IncrementalAlterConfigs API for syncing topic configurations. The API requires Kafka 2.3.0 or later".
3) Update syncTopicConfigs()
in MirrorSourceConnector.java
to call the updateTopicConfigsUsingIncrementalAlterConfigs()
instead of updateTopicConfigs()
if enable.incremental.alter.configs
is set to true.
...