You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "David Jacot (Jira)" <ji...@apache.org> on 2023/10/23 13:33:00 UTC

[jira] [Updated] (KAFKA-14509) Add ConsumerGroupDescribe API

     [ https://issues.apache.org/jira/browse/KAFKA-14509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jacot updated KAFKA-14509:
--------------------------------
    Labels: kip-848-preview  (was: )

> Add ConsumerGroupDescribe API
> -----------------------------
>
>                 Key: KAFKA-14509
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14509
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: David Jacot
>            Assignee: Max Riedel
>            Priority: Major
>              Labels: kip-848-preview
>
> The goal of this task is to implement the ConsumerGroupDescribe API as described [here|https://cwiki.apache.org/confluence/display/KAFKA/KIP-848%3A+The+Next+Generation+of+the+Consumer+Rebalance+Protocol#KIP848:TheNextGenerationoftheConsumerRebalanceProtocol-ConsumerGroupDescribeAPI]; and to implement the related changes in the admin client as described [here|https://cwiki.apache.org/confluence/display/KAFKA/KIP-848%3A+The+Next+Generation+of+the+Consumer+Rebalance+Protocol#KIP848:TheNextGenerationoftheConsumerRebalanceProtocol-Admin#describeConsumerGroups].
> On the server side, this mainly requires the following steps:
>  # The request/response schemas must be defined (see ListGroupsRequest/Response.json for an example);
>  # Request/response classes must be defined (see ListGroupsRequest/Response.java for an example);
>  # The API must be defined in KafkaApis (see KafkaApis#handleDescribeGroupsRequest for an example);
>  # The GroupCoordinator interface (java file) must be extended for the new operations.
>  # The new operation must be implemented in GroupCoordinatorService (new coordinator in Java) whereas the GroupCoordinatorAdapter (old coordinator in Scala) should just reject the request.
> We could probably do 1) and 2) in one pull request and the remaining ones in another.
> On the admin client side, this mainly requires the followings steps:
>  * Define all the new java classes as defined in the KIP.
>  * Add the new API to KafkaAdminClient class.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)