[
https://issues.apache.org/jira/browse/HADOOP-8524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-8524:
----------------------------
Attachment: HADOOP-8524.patch
Hey,
That makes complete sense and I am also perfectly fine with the idea of marking
this as unstable. I do love the idea of proper traceability and can work on it
if no one's begun yet (or if you're not gonna be driving it yet). Do file one
and chalk it out.
This request arose out of Oozie configs however at my end, not purely MR but
yes the traceability will help there too.
I've attached a patch to mark the API unstable.
Thanks for the comment and for taking a look quickly!
> 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, 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
