You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Matthias J. Sax (Jira)" <ji...@apache.org> on 2026/06/04 19:15:00 UTC

[jira] [Updated] (KAFKA-20655) Mark KIP-1331 RPCs stable before release

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

Matthias J. Sax updated KAFKA-20655:
------------------------------------
    Priority: Blocker  (was: Major)

> Mark KIP-1331 RPCs stable before release
> ----------------------------------------
>
>                 Key: KAFKA-20655
>                 URL: https://issues.apache.org/jira/browse/KAFKA-20655
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: streams
>            Reporter: Alieh Saeedi
>            Assignee: Lucas Brutschy
>            Priority: Blocker
>             Fix For: 4.4.0
>
>
> Before the release ships KIP-1331, the three APIs whose wire scaffolding landed under KAFKA-20620 need to be flipped from unstable to stable once the broker-side TopologyDescriptionManager and matching client request manager are in.
> Scope:
> 1. Remove `"latestVersionUnstable": true` from:
>    - clients/src/main/resources/common/message/StreamsGroupHeartbeatRequest.json
>    - clients/src/main/resources/common/message/StreamsGroupDescribeRequest.json
>    - clients/src/main/resources/common/message/StreamsGroupTopologyDescriptionUpdateRequest.json
> 2. In StreamsGroupTopologyDescriptionUpdateRequest.java, revert the Builder back to `super(ApiKeys.STREAMS_GROUP_TOPOLOGY_DESCRIPTION_UPDATE)` (drop the `, true` opt-in).
> 3. Replace the stub `handleStreamsGroupTopologyDescriptionUpdate` in KafkaApis.scala (returns UNSUPPORTED_VERSION) with the real handler, if not already done by the manager sub-task.



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