hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8617) backport pure Java CRC32 calculator changes to branch-1
Date Tue, 24 Jul 2012 20:58:35 GMT

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

Brandon Li commented on HADOOP-8617:

I ran teragen/terasort/teravalidate tests with the branch-1 patches from this JIRA and that
of HDFS-496 and MAPREDUCE-782.

Here is the result of test-patch with all the patches:
Total time: 4 minutes 17 seconds

-1 overall.  

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

    +1 tests included.  The patch appears to include 3 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 appears to introduce 174 new Findbugs (version 2.0.0) warnings.{noformat}

The findbug warnings are not introduced by these patches. 
> backport pure Java CRC32 calculator changes to branch-1
> -------------------------------------------------------
>                 Key: HADOOP-8617
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8617
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: performance
>    Affects Versions: 1.2.0
>            Reporter: Brandon Li
>            Assignee: Brandon Li
>         Attachments: HADOOP-8617.patch
> Multiple efforts have been made gradually to improve the CRC performance in Hadoop. This
JIRA is to back port these changes to branch-1, which include HADOOP-6166, HADOOP-6148, HADOOP-7333.
> The related HDFS and MAPREDUCE patches (e.g., HDFS-496 and MAPREDUCE-782) will be uploaded
to their original JIRAs.

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