[
https://issues.apache.org/jira/browse/KAFKA-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866838#comment-15866838
]
ASF GitHub Bot commented on KAFKA-4665:
---------------------------------------
GitHub user vahidhashemian opened a pull request:
https://github.com/apache/kafka/pull/2550
KAFKA-4665: Normalize handling of non-existing topics/partitions in
fetching offsets
This PR brings some consistency around how non-existing topics or
partitions are handled when fetching offsets using different versions of offset
fetch API.
In particular, it now
* returns `UNKNOWN_TOPIC_OR_PARTITION` for non-existing topics or
partitions in versions 1 and later (similar to how it is done in version 0)
* throws a `KafkaException` when consumers consume from a non-existing
topic or partition, or from a topic to which they do not have Describe access.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vahidhashemian/kafka KAFKA-4665
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2550.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2550
----
----
> 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.15#6346)
