Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Tue, 17 Jan 2017 19:34:26 +0000 (UTC)
From: "Jason Gustafson (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.13035644.1484681613000.31324.1484681666588@Atlassian.JIRA>
In-Reply-To: <JIRA.13035644.1484681613000@Atlassian.JIRA>
References: <JIRA.13035644.1484681613000@Atlassian.JIRA> <JIRA.13035644.1484681613446@jira-lw-us.apache.org>
Subject: [jira] [Created] (KAFKA-4665) Inconsistent handling of non-existing
 topics in offset fetch handling
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 17 Jan 2017 19:34:55 -0000

Jason Gustafson created KAFKA-4665:
--------------------------------------

             Summary: Inconsistent handling of non-existing topics in offset fetch handling
                 Key: KAFKA-4665
                 URL: https://issues.apache.org/jira/browse/KAFKA-4665
             Project: Kafka
          Issue Type: Bug
          Components: consumer, core
            Reporter: Jason Gustafson
             Fix For: 0.10.3.0


For version 0 of the offset fetch API, the broker returns UNKNOWN_TOPIC_OR_PARTITION for any topics/partitions which do not exist at the time of fetching. In later versions, we skip this check. We do, however, continue to return UNKNOWN_TOPIC_OR_PARTITION for authorization errors (i.e. if the principal does not have Describe access to the corresponding topic). We should probably make this behavior consistent across versions.

Note also that currently the consumer raises {{KafkaException}} when it encounters an UNKNOWN_TOPIC_OR_PARTITION error in the offset fetch response, which is inconsistent with how we usually handle this error. This probably doesn't cause any problems currently only because of the inconsistency mentioned in the first paragraph above.


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