[
https://issues.apache.org/jira/browse/KAFKA-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840346#comment-15840346
]
Vahid Hashemian commented on KAFKA-4665:
----------------------------------------
{quote}
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.
{quote}
[~hachikuji] Do you mean we should avoid raising exceptions for partition level
errors?
([here|https://github.com/apache/kafka/blob/254e3b77d656a610f19efd1124802e073dfda4b8/core/src/main/scala/kafka/admin/AdminClient.scala#L130])
> 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
> 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)
