Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Wed, 13 Jan 2016 20:05:39 +0000 (UTC)
From: "Ismael Juma (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12929932.1452715508000.101914.1452715539774@Atlassian.JIRA>
In-Reply-To: <JIRA.12929932.1452715508000@Atlassian.JIRA>
References: <JIRA.12929932.1452715508000@Atlassian.JIRA>
 <JIRA.12929932.1452715508630@arcas>
Subject: [jira] [Created] (KAFKA-3100) Broker.createBroker should work if
 json is version > 2, but still compatible
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Ismael Juma created KAFKA-3100:
----------------------------------

             Summary: Broker.createBroker should work if json is version > 2, but still compatible
                 Key: KAFKA-3100
                 URL: https://issues.apache.org/jira/browse/KAFKA-3100
             Project: Kafka
          Issue Type: Improvement
          Components: core
    Affects Versions: 0.9.0.0
            Reporter: Ismael Juma
            Assignee: Ismael Juma
             Fix For: 0.9.0.1


Description from Jun:

In 0.9.0.0, the old consumer reads broker info directly from ZK and the code throws an exception if the version in json is not 1 or 2. This old consumer will break when we upgrade the broker json to version 3 in ZK in 0.9.1, which will be an issue. We overlooked this issue in 0.9.0.0. The easiest fix is probably not to check the version in ZkUtils.getBrokerInfo().

This way, as long as we are only adding new fields in broker json, we can preserve the compatibility.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)