[ https://issues.apache.org/jira/browse/SPARK-17495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883203#comment-15883203 ]
Tejas Patil edited comment on SPARK-17495 at 2/24/17 5:57 PM: -------------------------------------------------------------- [~rxin] : No probs. Any opinion about my comment from yesterday ? ie. https://issues.apache.org/jira/browse/SPARK-17495?focusedCommentId=15882161&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15882161 was (Author: tejasp): [~rxin] : No probs. Any opinion about my comment from yesterday ? > Hive hash implementation > ------------------------ > > Key: SPARK-17495 > URL: https://issues.apache.org/jira/browse/SPARK-17495 > Project: Spark > Issue Type: Sub-task > Components: SQL > Reporter: Tejas Patil > Assignee: Tejas Patil > Priority: Minor > Fix For: 2.2.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.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org