[
https://issues.apache.org/jira/browse/KAFKA-16928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859970#comment-17859970
]
José Armando García Sancio commented on KAFKA-16928:
----------------------------------------------------
Yes. Take it. Note that I have made changes to that type for:
# Update to existing KRaft RPCs and request handling -
[https://github.com/apache/kafka/pull/16235]
# Response handling and request sending for KRaft RPCs -
[https://github.com/jsancio/kafka/compare/kafka-16527-raft-rpcs-version-handling...jsancio:kafka:kafka-16529-raft-request-sending]
It would be good if your tests include those changes before reviewing and
merging.
The most important thing is that KRaft is able to use the methods in RaftUtil
to generate requests and responses for all of the supported RPC versions.
> Test all of the request and response methods in RaftUtil
> --------------------------------------------------------
>
> Key: KAFKA-16928
> URL: https://issues.apache.org/jira/browse/KAFKA-16928
> Project: Kafka
> Issue Type: Sub-task
> Reporter: José Armando García Sancio
> Assignee: 黃竣陽
> Priority: Major
>
> Add a RaftUtilTest test suite that checks that the request and response
> constructed by RaftUtil can be serialized to all of the support KRaft RPC
> versions.
> The RPCs are:
> # Fetch
> # FetchSnapshot
> # Vote
> # BeginQuorumEpoch
> # EndQuorumEpoch
> At the moment some of the RPCs are missing this should be worked after
> RaftUtil implements the creation of all KRaft RPCs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
