hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8525) Provide Improved Traceability for Configuration
Date Tue, 26 Jun 2012 21:38:44 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Robert Joseph Evans updated HADOOP-8525:

    Status: Open  (was: Patch Available)

Canceling patch after trying to use the results as part of MAPREDUCE-4375.  It is working
as designed, but with the history server we are getting a lot of {noformat}org.apache.hadoop.hdfs.DFSClient$DFSDataInputStream@129b073{noformat}
so we need to add in a way to include a name along with the InputStream when adding in a resource.
> 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
>         Attachments: HADOOP-8525.txt
> 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


View raw message