[
https://issues.apache.org/jira/browse/KAFKA-16936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated KAFKA-16936:
-----------------------------------
Description:
origin discussion:
[https://github.com/apache/kafka/pull/16260#issuecomment-2159632052]
The specific provider class can be defined by `slf4j.provider`[0]. Hence, we
can add the slf4j backends we care about to dependencies. With that, our
distributions will have different slf4j backends and it is safe as we will
define slf4j.provider in our script. Also, those slf4j backends will be
collected to "dependend-libs", and hence we can run kafka instance from source
code with specific provider too.
In short, the following tasks are included by this jira
1. upgrade slf4j from 1.7.36 to 2.0.9+
2. add a new system variable to script to define -Dslf4j.provider easily. By
default we use org.slf4j.reload4j.Reload4jServiceProvider
3. add other slf4j backend dependencies (optional)
This change needs KIP since slf4j declares that all
[0] https://www.slf4j.org/manual.html
was:
origin discussion:
[https://github.com/apache/kafka/pull/16260#issuecomment-2159632052]
The specific provider class can be defined by `slf4j.provider`[0]. Hence, we
can add the slf4j backends we care about to dependencies. With that, our
distributions will have different slf4j backends and it is safe as we will
define slf4j.provider in our script. Also, those slf4j backends will be
collected to "dependend-libs", and hence we can run kafka instance from source
code with specific provider too.
In short, the following tasks are included by this jira
1. upgrade slf4j from 1.7.36 to 2.0.9+
2. add a new system variable to script to define -Dslf4j.provider easily. By
default we use org.slf4j.reload4j.Reload4jServiceProvider
3. add other slf4j backend dependencies (optional)
[0] https://www.slf4j.org/manual.html
> Upgrade slf4k to 2.0.9 and integrate "-Dslf4j.provider" to kafka script
> -----------------------------------------------------------------------
>
> Key: KAFKA-16936
> URL: https://issues.apache.org/jira/browse/KAFKA-16936
> Project: Kafka
> Issue Type: New Feature
> Reporter: Chia-Ping Tsai
> Assignee: Muralidhar Basani
> Priority: Major
> Labels: need-kip
>
> origin discussion:
> [https://github.com/apache/kafka/pull/16260#issuecomment-2159632052]
> The specific provider class can be defined by `slf4j.provider`[0]. Hence, we
> can add the slf4j backends we care about to dependencies. With that, our
> distributions will have different slf4j backends and it is safe as we will
> define slf4j.provider in our script. Also, those slf4j backends will be
> collected to "dependend-libs", and hence we can run kafka instance from
> source code with specific provider too.
> In short, the following tasks are included by this jira
> 1. upgrade slf4j from 1.7.36 to 2.0.9+
> 2. add a new system variable to script to define -Dslf4j.provider easily. By
> default we use org.slf4j.reload4j.Reload4jServiceProvider
> 3. add other slf4j backend dependencies (optional)
> This change needs KIP since slf4j declares that all
> [0] https://www.slf4j.org/manual.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
