[
https://issues.apache.org/jira/browse/MAPREDUCE-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094799#comment-13094799
]
Robert Joseph Evans commented on MAPREDUCE-2864:
------------------------------------------------
This is a quick note that the patch does not apply to 0.23 branch because one
of the lines in yar-default.xml has a version number in it
{code}
<
<!--<value>~/Workspace/eclipse-workspace/yarn/yarn-mapreduce/yarn-mapreduce-app/target/yarn-mapreduce-app-0.24.0-SNAPSHOT.jar</value>-->
---
>
> <!--<value>~/Workspace/eclipse-workspace/yarn/yarn-mapreduce/yarn-mapreduce-app/target/yarn-mapreduce-app-0.23.0-SNAPSHOT.jar</value>-->
{code}
I can make a separate patch for it if necessary after the reviews are in.
> Renaming of configuration property names in yarn
> ------------------------------------------------
>
> Key: MAPREDUCE-2864
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2864
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobhistoryserver, mrv2, nodemanager, resourcemanager
> Affects Versions: 0.23.0, 0.24.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Fix For: 0.23.0, 0.24.0
>
> Attachments: MR-2864-v1.patch, MR-2864-v2.patch, update.pl,
> yarnConfigs.csv
>
>
> Now that YARN has been put in to trunk we should do something similar to
> MAPREDUCE-849. We should go back and look at all of the configurations that
> have been added in and rename them as needed to be consistent and subdivided
> by component.
> # We should use all lowercase in the config names. e.g., we should use
> appsmanager instead of appsManager etc.
> # history server config names should be prefixed with mapreduce instead of
> yarn.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
