[
https://issues.apache.org/jira/browse/MAPREDUCE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14262099#comment-14262099
]
Hudson commented on MAPREDUCE-6149:
-----------------------------------
FAILURE: Integrated in Hadoop-Yarn-trunk #792 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/792/])
MAPREDUCE-6149. Document override log4j.properties in MR job. Contributed by
Junping Du. (harsh: rev 6621c3598e22279cde11eca73cfb5619a8bc8dee)
*
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/resources/mapred-default.xml
* hadoop-mapreduce-project/CHANGES.txt
> 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
> Fix For: 2.7.0
>
> Attachments: MAPREDUCE-6149-v2.patch, MAPREDUCE-6149-v3.patch,
> MAPREDUCE-6149.patch
>
>
> 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)
