THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- We fallback to using
alterConfigs
automatically ifincrementalAlterConfigs
is not supported, we . We need to unify the semantics if we want to do this heuristically, so we choose to give this privilege to users by adding --disable-incremental. - we keep existing scripts unchanged and add an "--enable-incremental" flag for new servers in Kafka 3.X, and remove it in Kafka 4.X. In this way we move the incompatible process to 4.X, I'm inclined to do it as soon as possible since it's inevitable.
- We just forward all invocations of alterConfigs to incrementalAlterConfigs. Similar to first one, we need to unify the semantics, it's not recommend since alterConfigs is deprecated and we just leave it as it was.