You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Hana1025 (via GitHub)" <gi...@apache.org> on 2026/05/17 04:33:57 UTC
[PR] KAFKA-9479: Print describe --state header once for multiple groups [kafka]
Hana1025 opened a new pull request, #22301:
URL: https://github.com/apache/kafka/pull/22301
When describing multiple consumer groups with --state (including --all-groups), compute column widths across all groups and print the header once.
Delete this text and replace it with a detailed description of your change. The
PR title and body will become the squashed commit message.
If you would like to tag individuals, add some commentary, upload images, or
include other supplemental information that should not be part of the eventual
commit message, please use a separate comment.
If applicable, please include a summary of the testing strategy (including
rationale) for the proposed change. Unit and/or integration tests are expected
for any behavior change and system tests should be considered for larger
changes.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] KAFKA-9479: Print describe --state header once for multiple groups [kafka]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #22301:
URL: https://github.com/apache/kafka/pull/22301#issuecomment-6307503680
This PR is being marked as stale since it has not had any activity in 90 days. If you
would like to keep this PR alive, please leave a comment asking for a review. If the PR has
merge conflicts, update it with the latest from the base branch.
<p>
If you are having difficulty finding a reviewer, please reach out on the
[mailing list](https://kafka.apache.org/contact).
<p>
If this PR is no longer valid or desired, please feel free to close it. If no activity
occurs in the next 30 days, it will be automatically closed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] KAFKA-9479: Print describe --state header once for multiple groups [kafka]
Posted by "Hana1025 (via GitHub)" <gi...@apache.org>.
Hana1025 commented on PR #22301:
URL: https://github.com/apache/kafka/pull/22301#issuecomment-4519868551
> @Hana1025 Pease provide sample output before and after with no groups, single group and multiple groups.
@smjn Thanks for the review. Sample output for kafka-consumer-groups.sh --describe --state is below (using --bootstrap-server localhost:9092).
No consumer groups (--all-groups on a cluster with no groups)
Before / After: (no table output)
printStates returns immediately when there are no printable groups.
Single group (--group group1 --state)
Before / After: (unchanged — one header and one data row)
GROUP COORDINATOR (ID) ASSIGNMENT-STRATEGY STATE #MEMBERS
group1 localhost:9092 (1) range Stable 1
Multiple groups (--all-groups with group1 and group2)
Before: header repeated for each group
GROUP COORDINATOR (ID) ASSIGNMENT-STRATEGY STATE #MEMBERS
group1 localhost:9092 (1) range Stable 1
GROUP COORDINATOR (ID) ASSIGNMENT-STRATEGY STATE #MEMBERS
group2 localhost:9092 (1) range Stable 1
After: header printed once; column widths computed across all groups
GROUP COORDINATOR (ID) ASSIGNMENT-STRATEGY STATE #MEMBERS
group1 localhost:9092 (1) range Stable 1
group2 localhost:9092 (1) range Stable 1
The same behavior applies when multiple groups are specified with repeated --group flags (e.g. --group group1 --group group2 --state).
Also pushed commit b7db1be with a regression test that asserts the state header is printed only once for multiple --group --state.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] KAFKA-9479: Print describe --state header once for multiple groups [kafka]
Posted by "smjn (via GitHub)" <gi...@apache.org>.
smjn commented on PR #22301:
URL: https://github.com/apache/kafka/pull/22301#issuecomment-4471867423
@Hana1025
Pease provide sample output before and after with no groups, single groups and multiple groups as a comment.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] KAFKA-9479: Print describe --state header once for multiple groups [kafka]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #22301:
URL: https://github.com/apache/kafka/pull/22301#issuecomment-4531560654
A label of 'needs-attention' was automatically added to this PR in order to raise the
attention of the committers. Once this issue has been triaged, the `triage` label
should be removed to prevent this automation from happening again.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] KAFKA-9479: Print describe --state header once for multiple groups [kafka]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #22301:
URL: https://github.com/apache/kafka/pull/22301#issuecomment-6514083554
A label of 'needs-attention' was automatically added to this PR in order to raise the
attention of the committers. Once this issue has been triaged, the `triage` label
should be removed to prevent this automation from happening again.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org