[
https://issues.apache.org/jira/browse/HDFS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294308#comment-13294308
]
Hadoop QA commented on HDFS-402:
--------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12531921/hdfs-402.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test
files.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.server.namenode.metrics.TestNameNodeMetrics
org.apache.hadoop.hdfs.TestFileLengthOnClusterRestart
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/2653//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2653//console
This message is automatically generated.
> Display the server version in dfsadmin -report
> ----------------------------------------------
>
> Key: HDFS-402
> URL: https://issues.apache.org/jira/browse/HDFS-402
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Uma Maheswara Rao G
> Priority: Minor
> Labels: newbie
> Attachments: HDFS-402.patch, HDFS-402.patch, HDFS-402.patch,
> hdfs-402.txt
>
>
> As part of HADOOP-5094, it was requested to include the server version in the
> dfsadmin -report, to avoid the need to screen scrape to get this information:
> bq. Please do provide the server version, so there is a quick and non-taxing
> way of determine what is the current running version on the namenode.
> Currently there is nothing in the dfs client protocol to query this
> information.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira