hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1237) Description for yarn.nodemanager.aux-services in yarn-default.xml is misleading
Date Wed, 11 Feb 2015 10:39:12 GMT

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

Hadoop QA commented on YARN-1237:

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision a4ceea6.

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

    {color:green}+0 tests included{color}.  The patch appears to be a documentation patch
that doesn't require tests.

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

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

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

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

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

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.

Test results: https://builds.apache.org/job/PreCommit-YARN-Build/6592//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6592//console

This message is automatically generated.

> Description for yarn.nodemanager.aux-services in yarn-default.xml is misleading
> -------------------------------------------------------------------------------
>                 Key: YARN-1237
>                 URL: https://issues.apache.org/jira/browse/YARN-1237
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Hitesh Shah
>            Assignee: Brahma Reddy Battula
>            Priority: Minor
>         Attachments: YARN-1237.patch
> Description states:
> "the valid service name should only contain a-zA-Z0-9_ and can not start with numbers"

> It seems to indicate only one service is supported. If multiple services are allowed,
it does not indicate how they should be specified i.e. comma-separated or space-separated?
If the service name cannot contain spaces, does this imply that space-separated lists are
also permitted?

This message was sent by Atlassian JIRA

View raw message