[
https://issues.apache.org/jira/browse/HIVE-24588?focusedWorklogId=533090&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-533090
]
ASF GitHub Bot logged work on HIVE-24588:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Jan/21 15:57
Start Date: 08/Jan/21 15:57
Worklog Time Spent: 10m
Work Description: zabetak opened a new pull request #1842:
URL: https://github.com/apache/hive/pull/1842
### What changes were proposed in this pull request?
Add new Junit Jupiter annotation/extension.
### Why are the changes needed?
Run easily unit tests using a specific log4j configuration with minimal
side-effects.
### Does this PR introduce _any_ user-facing change?
No
### How was this patch tested?
`mvn test -pl testutils -Dtest=TestLog4jConfigExtension`
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 533090)
Remaining Estimate: 0h
Time Spent: 10m
> 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
> Time Spent: 10m
> 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)
