You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2015/05/31 22:06:17 UTC
[jira] [Resolved] (HADOOP-12021) Augmenting Configuration to
accomodate
[ https://issues.apache.org/jira/browse/HADOOP-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lewis John McGibbney resolved HADOOP-12021.
-------------------------------------------
Resolution: Not A Problem
Thanks to everyone who commented here. Greatly appreciated.
> Augmenting Configuration to accomodate <description>
> ----------------------------------------------------
>
> Key: HADOOP-12021
> URL: https://issues.apache.org/jira/browse/HADOOP-12021
> Project: Hadoop Common
> Issue Type: New Feature
> Components: conf
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Priority: Minor
> Fix For: 1.3.0, 2.8.0
>
> Attachments: Screen Shot 2015-05-26 at 2.22.26 PM (2).png
>
>
> Over on the [common-dev|http://www.mail-archive.com/common-dev%40hadoop.apache.org/msg16099.html] ML I explained a use case which requires me to obtain the value of the Configuration <description> tags.
> [~cnauroth] advised me to raise the issue to Jira for discussion.
> I am happy to provide a patch so that the <description> values are parsed out of the various XML files and stored, and also that the Configuration class is augmented to provide accessors to accommodate the use case.
> I wanted to find out what people think about this one and whether I should check out Hadoop source and submit a patch. If you guys could provide some advice it would be appreciated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)