hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8525) Provide Improved Traceability for Configuration
Date Tue, 26 Jun 2012 22:30:44 GMT

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

Hadoop QA commented on HADOOP-8525:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 1 new or modified test files.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    -1 javadoc.  The javadoc tool appears to have generated 2 warning messages.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit

    -1 core tests.  The patch failed these unit tests in hadoop-common-project/hadoop-common:


    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/1142//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1142//console

This message is automatically generated.
> 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