THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Here is a table of all the changes:
| Command Name | Changes Needed |
|---|---|
| kafka-configs.sh | Support --zookeeper only for pre-startup connection initialization |
| kafka-leader-election.sh | Remove --zookeeper flag |
| kafka-preferred-leader-election.sh | Remove --zookeeper flag |
| kafka-reassign-partition.sh | Remove --zookeeper flag |
| kafka-topics.sh | Remove --zookeeper flag |
kafka-configs.sh
...
changes
Unlike all the other tools, kafka-configs.sh will keep the --zookeeper flag. It will be allowed only in two scenarios:
...
The rationale behind keeping the --zookeeper flag for this use-case is that we don't yet have an equivalent replacement. Although we are developing a new broker-side SCRAM API, this will only be usable once the brokers have started.
kafka-topics.sh changes
kafka-topic.sh will no longer support setting configurations. This functionality has been deprecated for a long time in favor of simply using kafka-configs.sh. This transition is a good time to remove this deprecated functionality, since it has never been supported in conjunction with --bootstrap-server.
We will support --if-exists and --if-not-exists when --bootstrap-server is specified. Previously, this was only supported if --zookeeper was specified.
Compatibility, Deprecation, and Migration Plan
...