[
https://issues.apache.org/jira/browse/KAFKA-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16256414#comment-16256414
]
huxihx commented on KAFKA-6219:
-------------------------------
Since the enclosing method captures all Throwables and explicitly prints them
as shown below,
try {
...
} catch {
case e: Throwable =>
printError(s"Executing consumer group command failed due to
${e.getMessage}", Some(e))
}
there is no need to capture them inside listGroup. Throwing to the caller is
the best choice.
[~ijuma] What do you think?
> 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)
