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

Neha Narkhede commented on KAFKA-1476:
--------------------------------------

[~balaji.sesha...@dish.com] Thanks for the patch. Few comments-
1. The "CONSUMER GROUPS
*****************" format is inconsistent with the other tools. For example, 
kafka-topics --list. Can we please remove it?
2. Currently, your tool only supports the list option. So the topic option is 
not required. 
3. The getConsumerGroups() API is better suited for ZkUtils.

Would you mind addressing the other feature requirements as well? Alternately, 
we can limit this JIRA to list and describe.

> Get a list of consumer groups
> -----------------------------
>
>                 Key: KAFKA-1476
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1476
>             Project: Kafka
>          Issue Type: Wish
>          Components: tools
>    Affects Versions: 0.8.1.1
>            Reporter: Ryan Williams
>            Assignee: BalajiSeshadri
>              Labels: newbie
>             Fix For: 0.9.0
>
>         Attachments: KAFKA-1476-LIST-GROUPS.patch, KAFKA-1476-RENAME.patch, 
> KAFKA-1476.patch
>
>
> It would be useful to have a way to get a list of consumer groups currently 
> active via some tool/script that ships with kafka. This would be helpful so 
> that the system tools can be explored more easily.
> For example, when running the ConsumerOffsetChecker, it requires a group 
> option
> bin/kafka-run-class.sh kafka.tools.ConsumerOffsetChecker --topic test --group 
> ?
> But, when just getting started with kafka, using the console producer and 
> consumer, it is not clear what value to use for the group option.  If a list 
> of consumer groups could be listed, then it would be clear what value to use.
> Background:
> http://mail-archives.apache.org/mod_mbox/kafka-users/201405.mbox/%3cCAOq_b1w=slze5jrnakxvak0gu9ctdkpazak1g4dygvqzbsg...@mail.gmail.com%3e



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

Reply via email to