[
https://issues.apache.org/jira/browse/KAFKA-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254858#comment-16254858
]
huxihx edited comment on KAFKA-6219 at 11/17/17 8:55 AM:
---------------------------------------------------------
[~vahid] I've been thinking of that before opening this one. In KAFKA-5638 you
recommend we narrow down the minimum required permission for ListGroup. For
this jira, however, I am thinking whether it's okay for `listGroups` to capture
all exceptions and return the empty list. The ACL case here is just an example.
Does it make sense?
was (Author: huxi_2b):
[~vahid] I've been thinking of that before opening this one. In KAFKA-5638 you
recommend we narrow down the minimum required permission for ListGroup. For
this jira, however, I am thinking whether it's okay for `listGroups` to capture
all exceptions return the empty list. The ACL case here is just an example.
Does it make sense?
> Inconsistent behavior for kafka-consumer-groups
> -----------------------------------------------
>
> Key: KAFKA-6219
> URL: https://issues.apache.org/jira/browse/KAFKA-6219
> Project: Kafka
> Issue Type: Bug
> Components: admin
> Affects Versions: 1.0.0
> Reporter: huxihx
> Assignee: huxihx
>
> For example, when ACL is enabled, running kafka-consumer-groups.sh --describe
> to describe a group complains:
> `Error: Executing consumer group command failed due to Not authorized to
> access group: Group authorization failed.`
> However, running kafka-consumer-groups.sh --list otherwise returns nothing,
> confusing user whether there are no groups at all or something wrong happened.
> In `AdminClient.listAllGroups`, it captures all the possible exceptions and
> returns an empty List.
> It's better keep those two methods consistent. Does it make any sense?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
