You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Robert Joseph Evans (JIRA)" <ji...@apache.org> on 2012/06/21 22:47:42 UTC

[jira] [Commented] (HADOOP-8525) Provide Improved Traceability for Configuration

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

Robert Joseph Evans commented on HADOOP-8525:
---------------------------------------------

I think the only big change here is a small addition to the XML format, so that we can add in a list of previous files it was read from and remove the comment that more or less gives the same information.  Internally the Map storing this into will have to now point to a list instead of a single value.  It looks fairly straight forward.  
                
> Provide Improved Traceability for Configuration
> -----------------------------------------------
>
>                 Key: HADOOP-8525
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8525
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>            Priority: Trivial
>
> Configuration provides basic traceability to see where a config setting came from, but once the configuration is written out that information is written to a comment in the XML and then lost the next time the configuration is read back in.  It would really be great to be able to store a complete history of where the config came from in the XML, so that it can then be retrieved later for debugging.

--
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