hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2864) Renaming of configuration property names in yarn
Date Wed, 31 Aug 2011 19:44:10 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094827#comment-13094827

Robert Joseph Evans commented on MAPREDUCE-2864:

I don't know why it is failing but PreCommit-MAPREDUCE-Build on Jenkins has not passed since
Build #302 (May 24, 2011 4:40:56 PM)

That is 3 months.  It failing should not block the patch being reviewed.

> 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, update.pl,
> 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


View raw message