[
https://issues.apache.org/jira/browse/KAFKA-20248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18062497#comment-18062497
]
Lucas Brutschy commented on KAFKA-20248:
----------------------------------------
Yes, the rackId is not used yet in 4.2, so the client doesn't send it yet. It
would be good it add it.
> 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)
