kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damian Guy (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-4665) Inconsistent handling of non-existing topics in offset fetch handling
Date Thu, 08 Feb 2018 14:27:00 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Damian Guy updated KAFKA-4665:
------------------------------
    Fix Version/s:     (was: 1.1.0)
                   2.0.0

> 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
>            Assignee: Vahid Hashemian
>            Priority: Major
>             Fix For: 2.0.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
(v7.6.3#76005)

Mime
View raw message