You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ewen Cheslack-Postava (JIRA)" <ji...@apache.org> on 2017/01/13 08:48:26 UTC

[jira] [Commented] (KAFKA-4622) KafkaConsumer does not properly handle authorization errors from offset fetches

    [ https://issues.apache.org/jira/browse/KAFKA-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821415#comment-15821415 ] 

Ewen Cheslack-Postava commented on KAFKA-4622:
----------------------------------------------

[~hachikuji] You filed this 2 days ago and marked for 0.10.2.0 -- are you actually trying to get a patch in for this before release? It'd be fair to include in post feature-freeze fixes, but I want to get an idea of whether this is truly prioritized for the release (i.e. going to get a patch + committed in next couple of weeks) or if this is just aspirational.

> KafkaConsumer does not properly handle authorization errors from offset fetches
> -------------------------------------------------------------------------------
>
>                 Key: KAFKA-4622
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4622
>             Project: Kafka
>          Issue Type: Bug
>          Components: consumer
>    Affects Versions: 0.9.0.1, 0.10.0.1, 0.10.1.1
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>             Fix For: 0.10.2.0
>
>
> It's possible to receive both group and topic authorization exceptions from an OffsetFetch, but the consumer currently treats this as generic unexpected errors. We should probably return {{GroupAuthorizationException}} and {{TopicAuthorizationException}} to be consistent with the other consumer APIs. 



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