Versions Compared

Old Version 2

changes.mady.by.user Magesh kumar Nandakumar

Saved on

compared with

New Version 3

changes.mady.by.user Magesh kumar Nandakumar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents


Status

Current state: Under Discussion

Discussion thread: here [Change the link from the KIP proposal email archive to your own email thread]

...

  • Ability to control the config keys that can be overridden. For e.g. an administrator might never want the broker endpoint to be overridden
  • Ability to control the allowed values for configs that are overridden. This helps with administrators defining the bounds of their clusters and manage multi-tenant cluster efficiently For e.g. the administrator might never want the `send.buffer.bytes` to above say 512 kb
  • Ability to control the above based on connector types, client type (admin vs producer vs consumer), etc. 

...

Inaddition to the default implementation, the KIP also proposes to a few more implementations of ConnectorClientConfigPolicy that are outlined in the table below

Class NameAliasBehavior

NoneConnectorClientConfigPolicy

NoneDisallows any configuration overrides

PrincipalConnectorClientConfigPolicy

Principal

Allows override of  "sasl.jaas.config" for the producer, consumer and admin prefixes.  Enables the ability to use different principal per connector.

AllConnectorClientConfigPolicy

AllAllows override of all configurations for the producer, consumer and admin prefixes. 

Since the users can specify any of these policies, the connectors itself should not rely on these configurations to be available. The overrides are to be used purely from an operational perspective.

...