You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Chia-Ping Tsai (Jira)" <ji...@apache.org> on 2025/02/17 12:47:00 UTC
[jira] [Resolved] (KAFKA-18784) Fix ConsumerWithLegacyMessageFormatIntegrationTest
[ https://issues.apache.org/jira/browse/KAFKA-18784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chia-Ping Tsai resolved KAFKA-18784.
------------------------------------
Resolution: Fixed
trunk: https://github.com/apache/kafka/commit/2b6e868538490837e4bc18c17708f42e5ae96a58
4.0: https://github.com/apache/kafka/commit/c4ea05f68411383eefe326e76202e2c534c71a2e
> Fix ConsumerWithLegacyMessageFormatIntegrationTest
> --------------------------------------------------
>
> Key: KAFKA-18784
> URL: https://issues.apache.org/jira/browse/KAFKA-18784
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Reporter: Ismael Juma
> Assignee: PoAn Yang
> Priority: Blocker
> Fix For: 4.0.0
>
>
> This test is meant to exercise the consumer with old message formats, but it's not actually doing that (the code to produce with old record formats was removed). To fix the test, we can use the `Log` class to write with old record formats.
> This test is still useful because brokers can still return records with old formats if the data was written to the log with the old format and never deleted. Another case is for compacted topics since we don't force the rewrite to the new message format with versions older than 4.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)