Versions Compared

Key

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

...

  • The API requires AclOperation.ALTER on ResourceType.CLUSTER.
  • The API request contains a list of FeatureUpdate that need to be applied, as explained below (see Validations section for more details):

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

      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)

      .

    • Downgrade or deletion of feature version level, is not a regular operation/intent. As an override, each item optionally can specify This is only attempted in the controller if item sets an allowDowngrade flag, to convey user intent to attempt max version level downgrade/deletion. Note that despite this allowDowngrade flag being set, certain downgrades may be rejected by the controller if it is deemed impossible.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.

...

  • X is the existing finalized feature max version level specified in '/features' ZK node.
  • Y is the new finalized feature max version level, specified as part of some FeatureUpdate, in the ApiKeys.UPDATE_FEATURES API request.

...