[
https://issues.apache.org/jira/browse/KAFKA-18396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914693#comment-17914693
]
TengYao Chi edited comment on KAFKA-18396 at 1/20/25 2:13 PM:
--------------------------------------------------------------
Hi [~dajac]
In short, this is not a must-do item for version 4.0, as `log4j-1.2-api`
already provides log4j1 compatibility mode for log4j2.
The reason why this issue hasn't been addressed yet:
In log4j1, we used properties files as the configuration format, which has a
flat structure where new configuration entries can override old ones. However,
in log4j2, we decided to use YAML as our configuration format, which has a
hierarchical structure. Since we accept multiple configuration sources, we need
to handle configuration conflicts and ensure new configuration entries can
properly override old ones. This is straightforward in the properties format
but becomes tricky in the YAML format.
I'm still working on it.
was (Author: JIRAUSER305181):
Hi [~dajac] ,
In short, this is not a must-do item for version 4.0, as `log4j-1.2-api`
already provides log4j1 compatibility mode for log4j2.
The reason why this issue hasn't been addressed yet:
In log4j1, we used properties files as the configuration format, which has a
flat structure where new configuration entries can override old ones. However,
in log4j2, we decided to use YAML as our configuration format, which has a
hierarchical structure. Since we accept multiple configuration sources, we need
to handle configuration conflicts and ensure new configuration entries can
properly override old ones. This is straightforward in the properties format
but becomes tricky in the YAML format.
I'm still working on it.
> Migrate log4j1 configuration to log4j2 in KafkaDockerWrapper
> ------------------------------------------------------------
>
> Key: KAFKA-18396
> URL: https://issues.apache.org/jira/browse/KAFKA-18396
> Project: Kafka
> Issue Type: Improvement
> Reporter: TengYao Chi
> Assignee: TengYao Chi
> Priority: Blocker
> Fix For: 4.0.0
>
>
> After log4j migration, we need to update the logging configuration in
> {{KafkaDockerWrapper}} from log4j1 to log4j2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
