[
https://issues.apache.org/jira/browse/HADOOP-9088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504886#comment-13504886
]
Todd Lipcon commented on HADOOP-9088:
-------------------------------------
I don't think HashPartitioner can be changed to use anything but
Object.hashCode (which we assume the user has implemented). Changing
WritableComparator to use a different hash hardly seems worth it. Have you seen
cases where the existing hash code causes poor distribution?
Also, I don't think we can change the default hashcode for existing types,
since it would change user-visible partitioning behavior. Adding a new
TextPartitioner which uses Murmur3 sounds useful, if you can show that there
are indeed real-world datasets where the "poor hash behavior" of the existing
partitioner causes skew.
> Add Murmur3 hash
> ----------------
>
> Key: HADOOP-9088
> URL: https://issues.apache.org/jira/browse/HADOOP-9088
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Radim Kolar
> Assignee: Radim Kolar
> Attachments: murmur3-2.txt, murmur3-3.txt, murmur3.txt
>
>
> faster and better then murmur2
--
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
