Versions Compared

Old Version 7

changes.mady.by.user Colin McCabe

Saved on

compared with

New Version 8

changes.mady.by.user Jason Gustafson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Drop support for --authorizer in kafka-acls.sh

...

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 NameChanges Needed
kafka-configs.shSupport --zookeeper only for pre-startup connection initialization
kafka-preferred-replica-election.shRemove this tool
kafka-reassign-partition.shRemove --zookeeper flag
kafka-topics.shRemove --zookeeper flag
kafka-acls.shRemove --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

kafka-acls.sh will no longer support directly updating ACLs through AclAuthorizer extensions. Instead users will be expected to update ACLs through the admin client by providing the --bootstrap-server argument.

Compatibility, Deprecation, and Migration Plan

...