Vincent Bernat created KAFKA-6344:
-------------------------------------
Summary: 0.8.2 clients will store invalid configuration in ZK for
Kafka 1.0 brokers
Key: KAFKA-6344
URL: https://issues.apache.org/jira/browse/KAFKA-6344
Project: Kafka
Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Vincent Bernat
Hello,
When using a Kafka 0.8.2 Scala client, the "changeTopicConfig" method from
AdminUtils will write the topic name to /config/changes/config_change_XXXXX.
Since 0.9, it is expected to have a JSON string and brokers will bail out if it
is not the case with a java.lang.IllegalArgumentException with message "Config
change notification has an unexpected value. The format is:{\"version\" : 1,
\"entity_type\":\"topics/clients\", \"entity_name\" : \"topic_name/client_id\"}
or {\"version\" : 2, \"entity_path\":\"entity_type/entity_name\"}. Received:
\"dns\"". Moreover, the broker will shutdown after this error.
As 1.0 brokers are expected to accept 0.8.x clients, either highlight in the
documentation this doesn't apply to AdminUtils or accept this "version 0"
format.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
