You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Stamatis Zampetakis (Jira)" <ji...@apache.org> on 2022/06/09 16:42:00 UTC

[jira] [Assigned] (HIVE-26309) Remove Log4jConfig junit extension in favor LoggerContextSource

     [ https://issues.apache.org/jira/browse/HIVE-26309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stamatis Zampetakis reassigned HIVE-26309:
------------------------------------------


> Remove Log4jConfig junit extension in favor LoggerContextSource
> ---------------------------------------------------------------
>
>                 Key: HIVE-26309
>                 URL: https://issues.apache.org/jira/browse/HIVE-26309
>             Project: Hive
>          Issue Type: Task
>          Components: Testing Infrastructure
>    Affects Versions: 4.0.0-alpha-1
>            Reporter: Stamatis Zampetakis
>            Assignee: Stamatis Zampetakis
>            Priority: Minor
>
> The Log4JConfig JUnit extension was introduced by HIVE-24588 in order to facilitate running tests with a specific log4j2 configuration.
> However, there is a very similar and seemingly more powerful JUnit extension in the official LOG4J2 release/repo, i.e., [LoggerContextSource|https://github.com/apache/logging-log4j2/blob/eedc3cdb6be6744071f8ae6dcfb37b26b1fc0940/log4j-core/src/test/java/org/apache/logging/log4j/junit/LoggerContextSource.java]. 
> The goal of this JIRA is to remove code related to Log4jConfig from Hive repo and replace its usages with LoggerContextSource. By doing this we reduce the maintenance overhead for the Hive community and reduce the dependencies to log4j-core.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)