spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tejas Patil (JIRA)" <>
Subject [jira] [Updated] (SPARK-17495) Hive hash implementation
Date Tue, 17 Jan 2017 05:55:26 GMT


Tejas Patil updated SPARK-17495:
    Issue Type: Sub-task  (was: Improvement)
        Parent: SPARK-19256

> Hive hash implementation
> ------------------------
>                 Key: SPARK-17495
>                 URL:
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>            Reporter: Tejas Patil
>            Assignee: Tejas Patil
>            Priority: Minor
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message