hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2410) Further clanup hardcoded configuration keys
Date Fri, 07 Oct 2011 00:15:29 GMT

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

Hadoop QA commented on HDFS-2410:

+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 156 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

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

    +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 passed unit tests in .

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

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

This message is automatically generated.
> Further clanup hardcoded configuration keys
> -------------------------------------------
>                 Key: HDFS-2410
>                 URL: https://issues.apache.org/jira/browse/HDFS-2410
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: data-node, name-node, test
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>            Priority: Minor
>         Attachments: HDFS-2410.txt
> HDFS code is littered with hardcoded config key names. This jira changes to use DFSConfigKeys

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