THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
DescribeConfigs Request (Version: 1) => [resource [config_name]] include_synonyms
resource => resource_type resource_name
resource_type => INT8
resource_name => STRING
config_name => STRING
include_synonyms => BOOLEAN
DescribeConfigs Response (Version: 1) => throttle_time_ms [entities]
throttle_time_ms => INT32
entities => error_code error_message resource [configs]
error_code => INT16
error_message => STRING
resource => resource_type resource_name
resource_type => INT8
resource_name => STRING
configs => [config_entry [synonym]] <= Added [synonym]
config_entry =>
config_name => STRING
config_value => NULLABLE_STRING
read_only => BOOLEAN
config_source => INT8 <= Replaced boolean is_default with more generic config_source (see below for values)
is_sensitive => BOOLEAN
synonym => <= NEW
config_name => STRING
config_value => NULLABLE_STRING
config_source => INT8 <= may be one of (TOPIC|DYNAMIC_BROKER|DYNAMIC_DEFAULT_BROKER|STATIC_BROKER|DEFAULT) |
When MetadataRequest version is increased after 1.1.0 release, a new error code ENDPOINT_NOT_FOUND_ON_LEADER will be added to notify clients when a listener is available on the broker used to obtain metadata, but not on the leader of a partition. This could be a transient error when listeners are added and will be retried in the same way as LEADER_NOT_AVAILABLE. Broker will continue to return LEADER_NOT_AVAILABLE to clients using older version of MetadataRequest. In 1.1.0, brokers will return LEADER_NOT_AVAILABLE instead of UNKNOWN_SERVER_ERROR in older versions.
Public Interface Changes
A new interface Reconfigurable will be added to notify reconfigurable objects of configuration changes. For example, metrics reporters that support reconfiguration can implement the interface Reconfigurable to enable reconfiguration without broker restart. The interface will also be implemented by all internal classes which support reconfiguration (e.g. ChannelBuilder)
...