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 "Junping Du (JIRA)" <ji...@apache.org> on 2014/11/02 05:47:33 UTC

[jira] [Updated] (MAPREDUCE-6149) Document override log4j.properties in MR job

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

Junping Du updated MAPREDUCE-6149:
----------------------------------
    Description: 
This new feature comes from MAPREDUCE-6052, some documentation requirements from Vinod below:
    Document the new config in mapred-default.xml
    Mention in that documentation that if no-scheme is given in the path, it defaults to a log4j file on the local FS.
    Modify the documentation of log-level configs to say that if you override to have your own log4j.properties file, the log-level configs may not work.


> Document override log4j.properties in MR job
> --------------------------------------------
>
>                 Key: MAPREDUCE-6149
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6149
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Junping Du
>            Assignee: Junping Du
>
> This new feature comes from MAPREDUCE-6052, some documentation requirements from Vinod below:
>     Document the new config in mapred-default.xml
>     Mention in that documentation that if no-scheme is given in the path, it defaults to a log4j file on the local FS.
>     Modify the documentation of log-level configs to say that if you override to have your own log4j.properties file, the log-level configs may not work.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)