[
https://issues.apache.org/jira/browse/KAFKA-20908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18103339#comment-18103339
]
sanghyeok An commented on KAFKA-20908:
--------------------------------------
[~schofielaj]
Thank you for letting me know.
My thought is that, if the API already returns the rack ID, it might be
reasonable to go ahead with this improvement even before the rack-aware
assignor is ready.
That said, would you prefer that we wait until the rack-aware assignor is
available before displaying the rack ID in the CLI?
> Consider exposing RACK-ID in kafka-share-groups.sh
> --------------------------------------------------
>
> Key: KAFKA-20908
> URL: https://issues.apache.org/jira/browse/KAFKA-20908
> Project: Kafka
> Issue Type: Improvement
> Components: tools
> Reporter: sanghyeok An
> Assignee: sanghyeok An
> Priority: Minor
> Labels: needs-kip, share-group
>
> ShareMemberDescription already exposes the optional rack ID of each share
> group member, but kafka-share-groups.sh --describe --members does not display
> it.
> Consider adding a RACK-ID column to the verbose member output (--describe
> --members --verbose).
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
