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

Hadoop QA commented on MAPREDUCE-2864:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12493643/MR-2864-v6.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 84 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/654//console

This message is automatically generated.

> 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, MR-2864-v5.patch, MR-2864-v6.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

        

Reply via email to