You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@crunch.apache.org by "Josh Wills (JIRA)" <ji...@apache.org> on 2012/12/23 21:54:12 UTC

[jira] [Updated] (CRUNCH-113) Move log4j hacking out of MRPipeline.enableDebug

     [ https://issues.apache.org/jira/browse/CRUNCH-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Wills updated CRUNCH-113:
------------------------------

    Attachment: CRUNCH-113v2.patch

Oof, I dropped the ball on this one pretty badly-- apologies. New patch uploaded to address the issues you mentioned.
                
> 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, CRUNCH-113v2.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