You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2020/12/01 23:56:00 UTC
[jira] [Resolved] (KAFKA-10729) KIP-482: Bump remaining RPC's to
use tagged fields
[ https://issues.apache.org/jira/browse/KAFKA-10729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Gustafson resolved KAFKA-10729.
-------------------------------------
Fix Version/s: 2.8.0
Resolution: Fixed
> KIP-482: Bump remaining RPC's to use tagged fields
> --------------------------------------------------
>
> Key: KAFKA-10729
> URL: https://issues.apache.org/jira/browse/KAFKA-10729
> Project: Kafka
> Issue Type: Improvement
> Reporter: Gardner Vickers
> Assignee: Gardner Vickers
> Priority: Major
> Fix For: 2.8.0
>
>
> With [KIP-482|https://cwiki.apache.org/confluence/display/KAFKA/KIP-482%3A+The+Kafka+Protocol+should+Support+Optional+Tagged+Fields], the Kafka protocol gained support for tagged fields.
> Not all RPC's were bumped to use flexible versioning and tagged fields. We should bump the remaining RPC's and provide a new IBP to take advantage of tagged fields via the flexible versioning mechanism.
>
> The RPC's which need to be bumped are:
>
> {code:java}
> AddOffsetsToTxnRequest
> AddOffsetsToTxnResponse
> AddPartitionsToTxnRequest
> AddPartitionsToTxnResponse
> AlterClientQuotasRequest
> AlterClientQuotasResponse
> AlterConfigsRequest
> AlterConfigsResponse
> AlterReplicaLogDirsRequest
> AlterReplicaLogDirsResponse
> DescribeClientQuotasRequest
> DescribeClientQuotasResponse
> DescribeConfigsRequest
> DescribeConfigsResponse
> EndTxnRequest
> EndTxnResponse
> ListOffsetRequest
> ListOffsetResponse
> OffsetForLeaderEpochRequest
> OffsetForLeaderEpochResponse
> ProduceRequest
> ProduceResponse
> WriteTxnMarkersRequest
> WriteTxnMarkersResponse
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)