[
https://issues.apache.org/jira/browse/KAFKA-17278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897706#comment-17897706
]
Kevin Wu edited comment on KAFKA-17278 at 11/12/24 9:13 PM:
------------------------------------------------------------
The RPC version tests did not catch this because they do not cover the case
where the RPC received by the controller is a different version than what is
set up by the context. They test versions 13 to 17, but both replicas are on
the same version in each case.
was (Author: JIRAUSER306575):
The RPC version tests did not catch this because they do not cover the case
where the RPC received by the controller is a different version than what is
set up by the context. They test versions 13 to 17, but both replicas are on
the same version in each case.
FetchRequest version 15 introduces the ReplicaState field and deprecates
ReplicaId, which breaks compatibility for old controllers with version <15 in
the same kind of way as described in KAFKA-17276. To fix this we can make a
similar change to make ReplicaState also ignorable and additionally set
ReplicaId in case the receiving controller is running an older version.
> Figure out and fix why the RPC version tests in KafkaRaftClientTest didn't
> catch a bug in the Fetch schema
> ----------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-17278
> URL: https://issues.apache.org/jira/browse/KAFKA-17278
> Project: Kafka
> Issue Type: Sub-task
> Reporter: José Armando García Sancio
> Assignee: Kevin Wu
> Priority: Major
>
> Why wasn't this bug caught in the KafkaRaftClientTest suite:
> https://issues.apache.org/jira/browse/KAFKA-17276
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
