[
https://issues.apache.org/jira/browse/MAPREDUCE-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251040#comment-14251040
]
Harsh J commented on MAPREDUCE-6149:
------------------------------------
Thanks! The added caveats and the changed message appear good to me.
I looked at the container-log4j.properties and we'd likely want the CLA
appender defined as-is so the logging is properly placed in an area and file
that works with aggregation (so users may continue to be able to view logs from
UI)?
I don't think we can cover all necessities in the doc, so would it be OK with
you if we marked this as an advanced property in the description, with the
caveat being something such as {{Requires certain framework appenders properly
defined in the overriden file}}?
Other than this it looks good, +1 with something on the lines of above added.
Thanks again!
> 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
> Attachments: MAPREDUCE-6149-v2.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)
