You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Gopal V (JIRA)" <ji...@apache.org> on 2017/07/18 03:07:00 UTC

[jira] [Commented] (HIVE-17114) HoS: Possible skew in shuffling when data is not really skewed

    [ https://issues.apache.org/jira/browse/HIVE-17114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091039#comment-16091039 ] 

Gopal V commented on HIVE-17114:
--------------------------------

[~lirui]: Changing the ObjectInspectorUtils.hashCode() implementation breaks all existing bucketed tables, breaks SMB joins and Bucket map-joins.

Specifically this is a problem with Hive-on-Spark, which doesn't have an underlying partitioner implementation for the ReduceSinkDesc$ReducerTraits.UNIFORM trait.

> HoS: Possible skew in shuffling when data is not really skewed
> --------------------------------------------------------------
>
>                 Key: HIVE-17114
>                 URL: https://issues.apache.org/jira/browse/HIVE-17114
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Rui Li
>            Assignee: Rui Li
>            Priority: Minor
>
> Observed in HoS and may apply to other engines as well.
> When we join 2 tables on a single int key, we use the key itself as hash code in {{ObjectInspectorUtils.hashCode}}:
> {code}
>       case INT:
>         return ((IntObjectInspector) poi).get(o);
> {code}
> Suppose the keys are different but are all some multiples of 10. And if we choose 10 as #reducers, the shuffle will be skewed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)