hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-6149) Document override log4j.properties in MR job
Date Sun, 02 Nov 2014 04:47:33 GMT

     [ 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)

Mime
View raw message