THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Table of Contents
Status
Current state: Under Discussion Accepted
Discussion thread: : https://lists.apache.org/thread/xd28mgqy75stgsvp6qybzpljzflkqcsy
JIRA: https://issues.apache.org/jira/browse/KAFKA-16181
Released:
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
...
We have 2 methods in AdminClient for updating config, alterConfigs and incrementalAlterConfigs , the former has many restrictions and has been deprecated from 2.3.0. However, It's still used in ConfigCommand to update broker config and is resulting in a bug
, so I'm inclined to move it to Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-13788 incrementalAlterConfigs and provide a flag fallback to still use alterConfigs for new client to interact with old servers. There use alterConfigs if the server is under 2.3.0. There are some other reasons for this change:
...
There is no backward compatibility problems brought in because we are changing it in a compatible way.
We should pay attention to KAFKA-10140 in which we have a problem updating jmx configs using `incrementalAlterConfigs` but we can still update jmx configs using `alterConfigs`, however, the problem only appear when append/subtract list type config which is not supported by kafka-configs.sh, so it will not influence this KIP, and we leave it in another one when we try to support append/subtract in kafka-configs.sh.
Test Plan
new client tool with older server can be tested locally and using test cases.
...