[ https://issues.apache.org/jira/browse/SPARK-17495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15599246#comment-15599246 ]
Reynold Xin commented on SPARK-17495: ------------------------------------- [~tejasp] I am going to reopen this. I just realized the committed implementation doesn't work for all data types, and are mostly dead code. Can we push it to completion by implementing the remaining data types? > Hive hash implementation > ------------------------ > > Key: SPARK-17495 > URL: https://issues.apache.org/jira/browse/SPARK-17495 > Project: Spark > Issue Type: Improvement > Components: SQL > Reporter: Tejas Patil > Assignee: Tejas Patil > Priority: Minor > Fix For: 2.1.0 > > > Spark internally uses Murmur3Hash for partitioning. This is different from > the one used by Hive. For queries which use bucketing this leads to different > results if one tries the same query on both engines. For us, we want users to > have backward compatibility to that one can switch parts of applications > across the engines without observing regressions. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org