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 "Eli Collins (JIRA)" <ji...@apache.org> on 2010/11/28 21:39:38 UTC
[jira] Commented: (HADOOP-7052) misspelling of threshold in
conf/log4j.properties
[ https://issues.apache.org/jira/browse/HADOOP-7052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964585#action_12964585 ]
Eli Collins commented on HADOOP-7052:
-------------------------------------
+1
This should not affect the default behavior since according to the log4j docs "By default the repository-wide threshold is set to the lowest possible value, namely the level ALL." Unless this value was not overriding the same setting elsewhere, and will after this change, but I don't think that's the case.
> misspelling of threshold in conf/log4j.properties
> -------------------------------------------------
>
> Key: HADOOP-7052
> URL: https://issues.apache.org/jira/browse/HADOOP-7052
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 0.21.0
> Reporter: Jingguo Yao
> Attachments: HADOOP-7052.patch
>
> Original Estimate: 0.08h
> Remaining Estimate: 0.08h
>
> In "log4j.threshhold=ALL", threshhold is a misspelling of threshold. So "log4j.threshhold=ALL" has no effect on the control of log4j logging.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.