GitHub user vahidhashemian opened a pull request:

    https://github.com/apache/kafka/pull/1336

    KAFKA-3144: Report members with no assigned partitions in 
ConsumerGroupCommand

    This PR makes a couple of enhancements to the `--describe` option of 
`ConsumerGroupCommand`:
    1. Listing members with no assigned partitions.
    2. Showing the member id along with the owner of each partition (owner is 
supposed to be the logical application id and all members in the same group are 
supposed to set the same owner).
    
    Note: The third request on the corresponding JIRA (listing group active 
offsets for groups with no members for the new consumer) is not implemented as 
part of this PR.
    I suggest moving that into a separate JIRA as it seems to be a more 
involved change and potentially requires making changes to the server side too.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vahidhashemian/kafka KAFKA-3144

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/1336.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 #1336
    
----
commit 9e9561cd27ec7c81a86317bd2746ec8fb0b46c5e
Author: Vahid Hashemian <vahidhashem...@us.ibm.com>
Date:   2016-05-06T22:16:38Z

    KAFKA-3144: Report members with no assigned partitions in 
ConsumerGroupCommand
    
    This PR makes some enhancements to the implementation of the "--describe" 
option of ConsumerGroupCommand:
    1. Listing members with no assigned partitions.
    2. Showing the member id along with the owner of each partition (owner is 
supposed to be the logical application id and all members in the same group are 
supposed to set the same owner).
    
    Note: The third request on the corresponding JIRA (listing group active 
offsets for groups with no members for the new consumer) is not implemented as 
part of this PR.
    I suggest moving that into a separate JIRA as it seems to be a more 
involved change and potentially requires making changes to the server side too.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to