[
https://issues.apache.org/jira/browse/KAFKA-19290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17955696#comment-17955696
]
Chia-Ping Tsai commented on KAFKA-19290:
----------------------------------------
[~schofielaj]
{quote}
For ShareFetch, ShareAcknowledge, ShareGroupHeartbeat and ShareGroupDescribe,
the v0 RPCs are already released and cannot be retrospectively optimised. For
others, such as AlterShareGroupOffsetsResponse, the optimisation can be applied
provided it is done before AK 4.1 releases.
{quote}
IIRC, `mapKey` does not break the compatibility, so it should be fine to change
them in 4.1 - I file https://issues.apache.org/jira/browse/KAFKA-19361 to
enhance the documents
> Exploit mapKey optimisation in protocol requests and responses
> --------------------------------------------------------------
>
> Key: KAFKA-19290
> URL: https://issues.apache.org/jira/browse/KAFKA-19290
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Andrew Schofield
> Assignee: PoAn Yang
> Priority: Minor
>
> The mapKey optimisation can be used in some KIP-932 RPC schemas to improve
> efficiency of some key-based accesses.
> For ShareFetch, ShareAcknowledge, ShareGroupHeartbeat and ShareGroupDescribe,
> the v0 RPCs are already released and cannot be retrospectively optimised. For
> others, such as AlterShareGroupOffsetsResponse, the optimisation can be
> applied provided it is done before AK 4.1 releases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
