[
https://issues.apache.org/jira/browse/HDFS-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249021#comment-13249021
]
Hadoop QA commented on HDFS-3226:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521735/hdfs-3226.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 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+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:
org.apache.hadoop.hdfs.TestDatanodeBlockScanner
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/2219//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2219//console
This message is automatically generated.
> Allow GetConf tool to print arbitrary keys
> ------------------------------------------
>
> Key: HDFS-3226
> URL: https://issues.apache.org/jira/browse/HDFS-3226
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: tools
> Affects Versions: 2.0.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hdfs-3226.txt
>
>
> Currently the "hdfs getconf" tool can only print out certain keys, like the
> list of NNs, etc. It would be handy to allow it to fetch an arbitrary
> configuration. For example, users may wish to write shell scripts that
> interact with their hadoop cluster, and it is useful to be able to fetch
> configs like the name of the superuser, or the state of whether HA is enabled.
--
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
