[
https://issues.apache.org/jira/browse/KAFKA-20248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18062534#comment-18062534
]
Matthias J. Sax edited comment on KAFKA-20248 at 3/3/26 6:05 PM:
-----------------------------------------------------------------
What is the intended scope of this ticket? It does mention `rackId` explicitly
– if it's only for `rackId`, it seems it's a sub-task for KAFKA-20116, and even
if this ticket is for all missing field, it still related.
I would also need to check the code to see, if a client side change is
sufficient, or if we also need broker side changes to actually pass the rack
information correctly into the assignor to begin with.
I did plan to actually work on this as part of KAFKA-20116, so we should first
sync about who is doing what to avoid duplicated work. You assigned this ticket
to yourself, so wondering if you are planning to work on this now? We should
get at least client side changes into AK 4.3 release, but code freeze is close.
was (Author: mjsax):
What is the intended scope of this ticket? It does mention `rackId` explicitly
– if it's only for `rackId`, it seems it's a sub-task for KAFKA-20116, and even
if this ticket is for all missing field, it still related.
I would also need to check the code to see, if a client side change is
sufficient, or if we also need broker side changes to actually pass the rack
information correctly into the assignor to begin with.
> Support fields that are not yet supported in StreamsGroup.
> ----------------------------------------------------------
>
> Key: KAFKA-20248
> URL: https://issues.apache.org/jira/browse/KAFKA-20248
> Project: Kafka
> Issue Type: Task
> Components: clients, streams
> Reporter: sanghyeok An
> Assignee: sanghyeok An
> Priority: Minor
> Labels: kip1071
>
> According to KIP-1071, the StreamsGroup protocol is required to support
> various fields. However, at the client level, this is not fully implemented
> yet.
> For example, as you can see in this code, KIP-1071 specifies that fields such
> as {{rackId}} should be set when present, but they are not currently included
> in the client request. {{rackId}} is an important factor in determining the
> group epoch in the Streams protocol.
> (https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/consumer/internals/StreamsMembershipManager.java#L295-L310)
> Although these fields are explicitly defined in the KIP-1071 document, they
> are not yet included in the actual client request. The goal of this ticket is
> to support such fields that are defined in KIP-1071 but are still missing
> from the client request.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
