Versions Compared

Key

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

...

  • The API request is a list of FeatureUpdate that need to be applied, as explained below:

    • Each item specifies the finalized feature to be added or updated or deleted, along with the new max feature version level value.

    • Max feature version level downgrades are not a regular operation. Each item optionally can specify an allowDowngrade flag, which can be used to allow version level downgrades (or deletions).
    • To add a new finalized feature version level, or update an existing one, the user must specify the version level starting from 1 (and increasing).
    • If a finalized feature needs to be permanently deleted, the user must specify a max version level value < 1, and should also set the allowDowngrade flag.

  • The API response contains an error code and an error message.
  • Changes to cluster-wide finalized minimum feature version level, can not be carried out using this API. This can be only done as explained later under Feature version deprecation section.

To help explain things better, below are the request and response definitions for the new API to update features (also see section showing related pseudocode for the Admin API):

...

Feature version deprecation

Sometimes there can be a need to deprecate a specific feature version (see Non-goals section). This requirement translates to increasing the cluster-wide finalized minimum version level of one or more features in the ZK '/features' node. Such feature version deprecations are typically announced in advance to the Kafka community. Then, during a specific Kafka release the Controller module during it's startup sequence can be made to automatically increase the cluster-wide finalized min version level of the deprecated feature in the ZK '/features' node.

...