You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Mickael Maison (Jira)" <ji...@apache.org> on 2023/04/24 09:20:00 UTC
[jira] [Commented] (KAFKA-14712) Confusing error when writing downgraded FeatureImage
[ https://issues.apache.org/jira/browse/KAFKA-14712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715669#comment-17715669 ]
Mickael Maison commented on KAFKA-14712:
----------------------------------------
The ticket is still unassigned so moving to the next release.
> Confusing error when writing downgraded FeatureImage
> ----------------------------------------------------
>
> Key: KAFKA-14712
> URL: https://issues.apache.org/jira/browse/KAFKA-14712
> Project: Kafka
> Issue Type: Bug
> Components: kraft
> Reporter: David Arthur
> Priority: Minor
> Labels: good-first-issue
> Fix For: 3.5.0
>
>
> We have logic in ImageWriterOptions which forces any MetadataVersion lower than 3.3-IV0 to be treated as 3.0-IV1. This was because FeatureLevel records were not supported before 3.3-IV0.
> When FeatureLevel is written at an older version, the "loss handler" produces an error message warning the user that some metadata is being lost.
> For example, when writing a FeatureImage with flag "foo" at MetadataVersion 3.2-IV0, we get a message like:
> > Metadata has been lost because the following could not be represented in metadata version 3.0-IV1: feature flag(s): foo
> This is confusing since we told the image builder to use MetadataVersion 3.2-IV0, but 3.0-IV1 appears in the text.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)