[ 
https://issues.apache.org/jira/browse/HADOOP-8524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399344#comment-13399344
 ] 

Hudson commented on HADOOP-8524:
--------------------------------

Integrated in Hadoop-Mapreduce-trunk #1117 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1117/])
    HADOOP-8524. Allow users to get source of a Configuration parameter. 
(harsh) (Revision 1352689)

     Result = FAILURE
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1352689
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/conf/Configuration.java
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/conf/TestConfiguration.java

                
> 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
>             Fix For: 2.0.1-alpha
>
>         Attachments: HADOOP-8524.patch, HADOOP-8524.patch, 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

        

Reply via email to