You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2007/05/18 01:36:16 UTC

[jira] Commented: (HADOOP-1385) MD5Hash has a bad hash function

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

Hadoop QA commented on HADOOP-1385:
-----------------------------------

+1

http://issues.apache.org/jira/secure/attachment/12357585/1385.patch applied and successfully tested against trunk revision r539135.

Test results:   http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/156/testReport/
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/156/console

> MD5Hash has a bad hash function
> -------------------------------
>
>                 Key: HADOOP-1385
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1385
>             Project: Hadoop
>          Issue Type: Bug
>          Components: io
>    Affects Versions: 0.12.3
>            Reporter: Owen O'Malley
>         Assigned To: Owen O'Malley
>             Fix For: 0.13.0
>
>         Attachments: 1385.patch
>
>
> The MD5Hash class has a really bad hash function, that will cause most most md5s to hash to 0xFFFFFFxx leaving only the low order byte as meaningful. The problem comes from the automatic sign extension when promoting from byte to int.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.