Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1923031734.1258160619679.JavaMail.jira@brutus>
Date: Sat, 14 Nov 2009 01:03:39 +0000 (UTC)
From: "olivier gillet (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-1979) MurmurHash does not yield the same
 results as the reference C++ implementation when size % 4 >= 2
In-Reply-To: <946603811.1258112979584.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777783#action_12777783 ] 

olivier gillet commented on HBASE-1979:
---------------------------------------

The only use of the hash(...) function I found is in HRegionInfo.encodeRegionName (ryan, is that what you referred to?), but it seems to explicitly use JenkinsHash instead of Murmur.

> MurmurHash does not yield the same results as the reference C++ implementation when size % 4 >= 2
> -------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-1979
>                 URL: https://issues.apache.org/jira/browse/HBASE-1979
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: util
>    Affects Versions: 0.20.1
>            Reporter: olivier gillet
>            Assignee: olivier gillet
>            Priority: Trivial
>             Fix For: 0.21.0, 0.20.3
>
>         Attachments: HBASE-1979.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Last rounds of MurmurHash are done in reverse order. data[length - 3], data[length - 2] and data[length - 1] in the block processing the remaining bytes should be data[len_m +2], data[len_m + 1], data[len_m].

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