[
https://issues.apache.org/jira/browse/MAPREDUCE-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099156#comment-13099156
]
Robert Joseph Evans commented on MAPREDUCE-2864:
------------------------------------------------
I divided them by client, server, and internal, because that is how they are
provided by the user. It helped be to see what was happening and where the
configs were coming from. I will refactor them to all be in YarnConfiguration
and MRJobConfig.
> 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, MR-2864-v3.patch,
> MR-2864-v4.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
