[
https://issues.apache.org/jira/browse/HADOOP-8524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398697#comment-13398697
]
Hadoop QA commented on HADOOP-8524:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12532913/HADOOP-8524.patch
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 appears to have generated 13 warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
-1 findbugs. The patch appears to introduce 1 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-common-project/hadoop-common:
org.apache.hadoop.fs.viewfs.TestViewFsTrash
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1132//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1132//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-common.html
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1132//console
This message is automatically generated.
> Allow users to get source of a Configuration parameter
> ------------------------------------------------------
>
> Key: HADOOP-8524
> URL: https://issues.apache.org/jira/browse/HADOOP-8524
> Project: Hadoop Common
> Issue Type: Improvement
> Components: conf
> Affects Versions: 2.0.0-alpha
> Reporter: Harsh J
> Assignee: Harsh J
> Priority: Trivial
> Attachments: HADOOP-8524.patch
>
>
> When we load the various XMLs via the Configuration class, the source of the
> XML file (filename) is usually kept in the Configuration class but not
> exposed programmatically. It is presently exposed as comments such as "Loaded
> from mapred-site.xml" in the XML dump/serialization but can't be accessed
> otherwise (Via the Configuration API).
> For debugging/etc. purposes, it may be useful to expose this safely (such as
> an API for "where did this property come from?" queries for a specific
> property, via an API.
--
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
