Page History

...

AlterConfigs Request (Version: 1) => [resources] validate_only
  validate_only => BOOLEAN
  resources => resource_type resource_name [configs]
    resource_type => INT8
    resource_name => STRING
    configs => config_name config_value config_operation
      config_name => STRING
      config_value => STRING
      config_operation => INT8                                           // new addition

Request Semantics:

1. The changes done will be incremental in version 1, opposed to the atomic behavior in version 0. For instance in version 0 sending an update for producer_byte_rate for userA would result in removing all previous data and updating userA's config with producer_byte_rate. Now in version 1 opposed to version 0 it will either add or update the config set present in Zookeeper and keeps other existing configs.
2. By default in the broker we parse an AlterConfigRequest version 0 with Unknown operation and handle it with the currently existing behavior. Version 1 requests however must have the operation set to other than Unknown, otherwise an InvalidRequestException will be thrown.
3. Set operation also does Add if needed to be backward compatible with the existing ConfigCommand semantics.

...