THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Discussion thread: here
JIRA: none yet
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
...
The --zookeeper flag will be removed from all the places where it was deprecated in KIP-555, with only one exception which will be described in a little bit.
We will also remove support for the --authorizer in the ACL command. This was previously allowed for writes directly to the Zookeeper-based authorizer. Now support for changing ACLs is supported through the admin client (see KIP-332: Update AclCommand to use AdminClient API).
Here is a table of all the changes:
| Command Name | Changes Needed |
|---|---|
| kafka-configs.sh | Support --zookeeper only for pre-startup connection initialization |
| kafka-preferred-replica-election.sh | Remove this tool |
| kafka-reassign-partition.sh | Remove --zookeeper flag |
| kafka-topics.sh | Remove --zookeeper flag |
| kafka-acls.sh | Deprecate and eventually remove --authorizer, --authorizer-properties, and --zk-tls-config-file |
kafka-preferred-replica-election.sh
...
We will support --if-exists and --if-not-exists when --bootstrap-server is specified. Previously, this was only supported if --zookeeper was specified.
kafka-acls.sh changes
In kafka-acls.sh, support for directly updating ACLs through AclAuthorizer extensions will be deprecated and eventually removed in a major release. Instead users will be expected to update ACLs through the admin client by providing the --bootstrap-server argument.
Compatibility, Deprecation, and Migration Plan
...
The flags that are being removed immediately (excluding kafka-acls.sh) have already been deprecated for at least one release.
The migration plan is to use --bootstrap-server for these commands instead.
...