Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Sun, 16 Jun 2013 22:18:20 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12631205.1360214216477.122846.1371421100634@arcas>
In-Reply-To: <JIRA.12631205.1360214216477@arcas>
References: <JIRA.12631205.1360214216477@arcas>
Subject: [jira] [Commented] (YARN-387) Fix inconsistent protocol naming
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/YARN-387?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D136848=
18#comment-13684818 ]=20

Hadoop QA commented on YARN-387:
--------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest=
 attachment=20
  http://issues.apache.org/jira/secure/attachment/12588044/YARN-387-2013061=
6.txt
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author=
 tags.

    {color:green}+1 tests included{color}.  The patch appears to include 33=
 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the =
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any =
warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:e=
clipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new =
Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not incre=
ase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hado=
op-common-project/hadoop-common hadoop-mapreduce-project/hadoop-mapreduce-c=
lient/hadoop-mapreduce-client-app hadoop-mapreduce-project/hadoop-mapreduce=
-client/hadoop-mapreduce-client-hs hadoop-mapreduce-project/hadoop-mapreduc=
e-client/hadoop-mapreduce-client-jobclient hadoop-yarn-project/hadoop-yarn/=
hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/ha=
doop-yarn-applications-distributedshell hadoop-yarn-project/hadoop-yarn/had=
oop-yarn-client hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-y=
arn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop=
-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager=
 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-reso=
urcemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-=
server-tests hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn=
-server-web-proxy hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit te=
sts.

Test results: https://builds.apache.org/job/PreCommit-YARN-Build/1271//test=
Report/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1271//co=
nsole

This message is automatically generated.
               =20
> Fix inconsistent protocol naming
> --------------------------------
>
>                 Key: YARN-387
>                 URL: https://issues.apache.org/jira/browse/YARN-387
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>            Priority: Blocker
>              Labels: incompatible
>         Attachments: YARN-387-20130616.txt
>
>
> We now have different and inconsistent naming schemes for various protoco=
ls. It was hard to explain to users, mainly in direct interactions at talks=
/presentations and user group meetings, with such naming.
> We should fix these before we go beta.=20

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira