Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@crunch.apache.org
Date: Tue, 29 Oct 2013 01:57:30 +0000 (UTC)
From: "Micah Whitacre (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <JIRA.12670616.1380161067223.15578.1383011850699@arcas>
In-Reply-To: <JIRA.12670616.1380161067223@arcas>
References: <JIRA.12670616.1380161067223@arcas>
Subject: [jira] [Commented] (CRUNCH-270) crunch-core includes
 log4j.properties
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CRUNCH-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807584#comment-13807584 ] 

Micah Whitacre commented on CRUNCH-270:
---------------------------------------

Yep looks like that information is logged using commons-logging at INFO level.  Not finding anything super authoritative but looks like commons-logging defaults the log level to INFO[1].  I haven't tested yet on a real cluster to ensure there isn't a default configuration that raises the level.

[1] - http://commons.apache.org/proper/commons-logging/guide.html#When_Info_Level_Instead_of_Debug

> crunch-core includes log4j.properties
> -------------------------------------
>
>                 Key: CRUNCH-270
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-270
>             Project: Crunch
>          Issue Type: Bug
>          Components: Core
>            Reporter: Chao Shi
>            Assignee: Josh Wills
>         Attachments: CRUNCH-270.patch
>
>
> I found crunch-core jar includes log4j.properties, which may override user's log4j configuration. 
> ./crunch-core/src/main/resources/log4j.properties
> ./crunch-scrunch/src/main/conf/log4j.properties
> I'm not sure if this was intended.


--
This message was sent by Atlassian JIRA
(v6.1#6144)