[
https://issues.apache.org/jira/browse/HDFS-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938804#comment-13938804
]
Hadoop QA commented on HDFS-6112:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12635222/HDFS-6112.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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 1.3.9) 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-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/6417//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6417//console
This message is automatically generated.
> NFS Gateway docs are incorrect for allowed hosts configuration
> --------------------------------------------------------------
>
> Key: HDFS-6112
> URL: https://issues.apache.org/jira/browse/HDFS-6112
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: nfs
> Affects Versions: 2.4.0
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Priority: Minor
> Attachments: HDFS-6112.patch
>
>
> The NFS gateway export configuration docs say that the machine name
> configuration can be "wildcards" and provides the example
> "{{host*.example.com}}". The term "wildcard" and this example might imply
> typical globbing semantics, but in fact what it actually supports is Java
> regular expressions. I think we should change the docs to make this clearer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
