[jira] [Resolved] (HIVE-24588) Run tests using specific log4j2 configuration conveniently

["Jesus Camacho Rodriguez (Jira)" <ji...@apache.org>]

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

Jesus Camacho Rodriguez resolved HIVE-24588.
--------------------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

Pushed to master, thanks [~zabetak]!

> Run tests using specific log4j2 configuration conveniently
> ----------------------------------------------------------
>
>                 Key: HIVE-24588
>                 URL: https://issues.apache.org/jira/browse/HIVE-24588
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Stamatis Zampetakis
>            Assignee: Stamatis Zampetakis
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> In order to reproduce a problem (e.g., HIVE-24569) or validate that a log4j2 configuration is working as expected it is necessary to run a test and explicitly specify which configuration should be used. Moreover, after the end of the test in question it is desirable to restore the old logging configuration that was used before launching the test to avoid affecting the overall logging output.
> The goal of this issue is to introduce a convenient & declarative way of running tests with log4j2 configurations based on Jupiter extensions and annotations. The test could like below:
> {code:java}
>   @Test
>   @Log4jConfig("test-log4j2.properties")
>   void testUseExplicitConfig() {
>     // Do something and assert
>   }
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)