Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4D0BB9089 for ; Thu, 21 Jun 2012 20:45:43 +0000 (UTC) Received: (qmail 58613 invoked by uid 500); 21 Jun 2012 20:45:43 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 58507 invoked by uid 500); 21 Jun 2012 20:45:42 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 58464 invoked by uid 99); 21 Jun 2012 20:45:42 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jun 2012 20:45:42 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id C1A7D14285F for ; Thu, 21 Jun 2012 20:45:42 +0000 (UTC) Date: Thu, 21 Jun 2012 20:45:42 +0000 (UTC) From: "Robert Joseph Evans (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <254722166.41071.1340311542797.JavaMail.jiratomcat@issues-vm> In-Reply-To: <746372576.39678.1340297743801.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HADOOP-8524) Allow users to get source of a Configuration parameter MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-8524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398835#comment-13398835 ] Robert Joseph Evans commented on HADOOP-8524: --------------------------------------------- Great I just filed HADOOP-8525 for this. If you want to work on it go right ahead, if not I will try to throw together a quick patch sometime this week. and +1 for this patch. Looks good to me. > 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