[
https://issues.apache.org/jira/browse/KAFKA-18354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-18354.
------------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
trunk:
https://github.com/apache/kafka/commit/106fd5f601df858ab0affd8967a07df0987e9ee1
4.0:
https://github.com/apache/kafka/commit/fd73b34193142aaf15a20d7efb4c7e53efb6c2ed
> Use log4j2 APIs to refactor LogCaptureAppender
> ----------------------------------------------
>
> Key: KAFKA-18354
> URL: https://issues.apache.org/jira/browse/KAFKA-18354
> Project: Kafka
> Issue Type: Improvement
> Reporter: Chia-Ping Tsai
> Assignee: 黃竣陽
> Priority: Minor
> Fix For: 4.0.0
>
>
> 1. we can leverage Configurator.setLevel to configure level directly
> 2. Each LogCaptureAppender instance should have different name as log4j2
> trace the appender by the name
> 3. LogLevelChange should be changed from list to map structure to ensure we
> don't reconfigure a class only once
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
