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

Posted to mapreduce-issues@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2014/07/22 22:32:41 UTC

[jira] [Commented] (MAPREDUCE-5992) native-task test logs should not write to console

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

Todd Lipcon commented on MAPREDUCE-5992:
----------------------------------------

I realized it's not a log4j issue at all. The native code logs directly to stderr without going through log4j. We should see if we can tie it into log4j via JNI.

> native-task test logs should not write to console
> -------------------------------------------------
>
>                 Key: MAPREDUCE-5992
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5992
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: task
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>
> Most of our unit tests are configured with a log4j.properties test resource so they don't spout a bunch of output to the console. We need to do the same for native-task.



--
This message was sent by Atlassian JIRA
(v6.2#6252)