[
https://issues.apache.org/jira/browse/HBASE-9631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776039#comment-13776039
]
Liang Xie commented on HBASE-9631:
----------------------------------
i think we can recommend a new bootstrap cluster to config murmur3.
for a existing cluster, if we change it on-the-fly, probably has some issues
for compatibility. since the murmur3 seems doesn't guarantee generate the same
result as murmur2, so the existing data's hash will probably has diff result
during change algo. (myabe MurmurHash3_x86_32 could reture same as murmur2, but
i am not sure right now yet)
> add murmur3 hash
> ----------------
>
> Key: HBASE-9631
> URL: https://issues.apache.org/jira/browse/HBASE-9631
> Project: HBase
> Issue Type: New Feature
> Components: util
> Affects Versions: 0.98.0
> Reporter: Liang Xie
> Assignee: Liang Xie
> Attachments: HBase-9631.txt
>
>
> MurmurHash3 is the successor to MurmurHash2. It comes in 3 variants - a
> 32-bit version that targets low latency for hash table use and two 128-bit
> versions for generating unique identifiers for large blocks of data, one each
> for x86 and x64 platforms.
> several open source projects have added murmur3 already, like cassandra,
> mahout, etc.
> I just port the murmur3 from MAHOUT-862. due to compatibility, let's keep the
> default Hash algo(murmur2) without changing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
