[
https://issues.apache.org/jira/browse/KAFKA-18738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926791#comment-17926791
]
Chia-Ping Tsai commented on KAFKA-18738:
----------------------------------------
Pardon me, is this ticket fixed already? it seems
DescribeShareGroupOffsetsRequest [0] is still using single group id
[0]
https://github.com/apache/kafka/blob/trunk/clients/src/main/resources/common/message/DescribeShareGroupOffsetsRequest.json#L25
> Revisit the DescribeShareGroupOffsets API to support multiple GroupIds in
> Request
> ---------------------------------------------------------------------------------
>
> Key: KAFKA-18738
> URL: https://issues.apache.org/jira/browse/KAFKA-18738
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Sanskar Jhajharia
> Assignee: Andrew Schofield
> Priority: Major
> Fix For: 4.1.0
>
>
> Currently the DescribeShareGroupOffsets API accepts a single Group ID per
> request. However the AdminClient.listShareGroupOffsets() methods which makes
> a call to this API actually can pass multiple group ids.
> Currently in the ListShareGroupOffsetsHandler
> [class|https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/admin/internals/ListShareGroupOffsetsHandler.java#L83],
> we have specified the code such that the AdminClient is explicitly passing
> just a single group ID, however this might be changes to support multiple
> GroupIds in the DescribeShareGroupOffsets similar to the corresponding
> Consumer Group offsets request.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
