Page History

...

The communication with ZK is built on top of the existing adminZKClient package. To be specific, the following two APIs will be leveraged to finish the process of user/client config changes.

/**
 * Update the config for a client and create a change notification so the change will propagate to other brokers.
 * If clientId is <default>, default clientId config is updated. ClientId configs are used only if <user, clientId>
 * and <user> configs are not specified.
 *
 * @param sanitizedClientId: The sanitized clientId for which configs are being changed
 * @param configs: The final set of configs that will be applied to the topic. If any new configs need to be added or
 * existing configs need to be deleted, it should be done prior to invoking this API
 *
 */
def changeClientIdConfig(sanitizedClientId: String, configs: Properties) {
  DynamicConfig.Client.validate(configs)
  changeEntityConfig(ConfigType.Client, sanitizedClientId, configs)
}

/**
 * Update the config for a <user> or <user, clientId> and create a change notification so the change will propagate to other brokers.
 * User and/or clientId components of the path may be <default>, indicating that the configuration is the default
 * value to be applied if a more specific override is not configured.
 *
 * @param sanitizedEntityName: <sanitizedUserPrincipal> or <sanitizedUserPrincipal>/clients/<clientId>
 * @param configs: The final set of configs that will be applied to the topic. If any new configs need to be added or
 * existing configs need to be deleted, it should be done prior to invoking this API
 *
 */
def changeUserOrUserClientIdConfig(sanitizedEntityName: String, configs: Properties) {
  if (sanitizedEntityName == ConfigEntityName.Default || sanitizedEntityName.contains("/clients"))
    DynamicConfig.Client.validate(configs)
  else
 DynamicConfig.User.validate(configs)
    changeEntityConfig(ConfigType.User, sanitizedEntityName, configs)
}

...