[
https://issues.apache.org/jira/browse/KAFKA-14056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039115#comment-18039115
]
PoAn Yang commented on KAFKA-14056:
-----------------------------------
[~ijuma] Yes, we have related test cases
ConsumerWithLegacyMessageFormatIntegrationTest. These cases append old format
records and check classic/async consumers can operate
offsetsForTimes/beginningOffsets/endOffsets. This validates broker can read old
format records successfully.
[https://github.com/apache/kafka/blob/trunk/clients/clients-integration-tests/src/test/java/org/apache/kafka/clients/consumer/ConsumerWithLegacyMessageFormatIntegrationTest.java]
If there is no other concern, I think we can resolve this issue. Thanks.
> Test reading of old messages formats in ZK-to-KRaft upgrade test
> ----------------------------------------------------------------
>
> Key: KAFKA-14056
> URL: https://issues.apache.org/jira/browse/KAFKA-14056
> Project: Kafka
> Issue Type: Task
> Components: kraft
> Affects Versions: 3.9.0
> Reporter: Ron Dagostino
> Assignee: Dhiyaneshwaran Radhakrishnan
> Priority: Blocker
> Fix For: 3.9.2
>
>
> Whenever we support ZK-to-KRaft upgrade we must confirm that we can still
> read messages with an older message format. We can no longer write such
> messages as of IBP 3.0 (which is the minimum supported with KRaft), but we
> must still support reading such messages with KRaft. Therefore, the only way
> to test this would be to write the messages with a non-KRaft cluster, upgrade
> to KRaft, and then confirm we can read those messages.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
