Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
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 requires the version match between the provider and slf4j-api.jar. Hence, users may encounter compatibility issue if they have added other providers jar into kafka classpath.
Attachments
Issue Links
- is related to
-
KAFKA-9366 Upgrade log4j to log4j2
- In Progress
- links to