You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "wenxin he (JIRA)" <ji...@apache.org> on 2017/06/21 03:32:00 UTC
[jira] [Commented] (HADOOP-14549) Use GenericTestUtils.setLogLevel
when available
[ https://issues.apache.org/jira/browse/HADOOP-14549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056926#comment-16056926 ]
wenxin he commented on HADOOP-14549:
------------------------------------
hi [~ajisakaa], I'll take this issue.
Before that I want to make sure:
1. Which one do you intend to do? Replacing all org.apache.log4j.Logger.setLevel where GenericTestUtils.setLogLevel available in *WHOLE* hadoop project or in some certain module like hadoop-tool?
2. GenericTestUtils.setLogLevel is still using org.apache.log4j.Level as parameter which is log4j1 api. In log4j2, this changed to org.apache.{color:red}logging{color}.log4j.Level. Is this OK for us to migration to log4j2?
> Use GenericTestUtils.setLogLevel when available
> -----------------------------------------------
>
> Key: HADOOP-14549
> URL: https://issues.apache.org/jira/browse/HADOOP-14549
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Akira Ajisaka
>
> Based on Brahma's [comment|https://issues.apache.org/jira/browse/HADOOP-14296?focusedCommentId=16054390&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16054390] in HADOOP-14296, it's better to use GenericTestUtils.setLogLevel as possible to make the migration easier.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org