[
https://issues.apache.org/jira/browse/CRUNCH-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498154#comment-13498154
]
Matthias Friedrich commented on CRUNCH-113:
-------------------------------------------
Just tried this with our WordCount example, but only got the "Could not find
console appender" message. That's because the "org.apache.crunch" logger
doesn't have an appender A, only the root logger has (it works with
LogManager.getRootLogger()).
What puzzles me is that I do get INFO messages from Hadoop on the console when
I run jobs using LocalJobRunner (that's due to our many log4j.properties
files). But when I use the (fixed) DebugLogging.enable() method, I only get
Hadoop messages on level WARN, which is less than before. Do you mean to set
this to DEBUG?
> Move log4j hacking out of MRPipeline.enableDebug
> ------------------------------------------------
>
> Key: CRUNCH-113
> URL: https://issues.apache.org/jira/browse/CRUNCH-113
> Project: Crunch
> Issue Type: Improvement
> Affects Versions: 0.3.0, 0.4.0
> Reporter: Josh Wills
> Assignee: Josh Wills
> Fix For: 0.5.0
>
> Attachments: CRUNCH-113.patch
>
>
> MRPipeline.enableDebug currently does some shenanigans with the log4j
> LogManager object to override external log4j configuration. After a lengthy
> thread, we came to the consensus that this was a bad idea, and so we're going
> to move the shenanigans out of MRPipeline and into a static method in
> crunch-test where they won't be able to do as much harm.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
