[
https://issues.apache.org/jira/browse/KAFKA-13935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-13935:
---------------------------------
Description:
We pass the IBP down to the log layer for checking things like compression
support. Currently, we are still reading this from KafkaConfig. In ZK mode this
is fine, but in KRaft mode, reading the IBP from the config is not supported.
Since KRaft only supports IBP/MetadataVersion greater than 3.0 (which supports
the compression mode we check for), we may be able to avoid using a dynamic
call and/or volatile to get the current version.
was:
We pass the IBP down to the log layer for checking things like compression
support. Currently, we are still reading this from KafkaConfig. In ZK mode this
is fine, but in KRaft mode, reading the IBP from the config is not supported.
Since KRaft only supports IBP/MetadataVersion greater than 3.0 (which supports
the compression modes we check for), we may be able to avoid using a dynamic
call and/or volatile to get the current version.
> Factor out IBP from Partition and Log code
> ------------------------------------------
>
> Key: KAFKA-13935
> URL: https://issues.apache.org/jira/browse/KAFKA-13935
> Project: Kafka
> Issue Type: Sub-task
> Affects Versions: 3.3.0
> Reporter: David Arthur
> Priority: Major
>
> We pass the IBP down to the log layer for checking things like compression
> support. Currently, we are still reading this from KafkaConfig. In ZK mode
> this is fine, but in KRaft mode, reading the IBP from the config is not
> supported.
> Since KRaft only supports IBP/MetadataVersion greater than 3.0 (which
> supports the compression mode we check for), we may be able to avoid using a
> dynamic call and/or volatile to get the current version.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
