You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2016/01/27 23:12:39 UTC

[jira] [Commented] (HIVE-12945) Bucket pruning: bucketing for -ve hashcodes have historical issues

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

Sergey Shelukhin commented on HIVE-12945:
-----------------------------------------

That appears to override the number rather than scan twice as much for both variants. Am I missing something?

> Bucket pruning: bucketing for -ve hashcodes have historical issues
> ------------------------------------------------------------------
>
>                 Key: HIVE-12945
>                 URL: https://issues.apache.org/jira/browse/HIVE-12945
>             Project: Hive
>          Issue Type: Bug
>          Components: Tez
>    Affects Versions: 2.0.0
>            Reporter: Gopal V
>            Assignee: Gopal V
>            Priority: Critical
>         Attachments: HIVE-12945.1.patch
>
>
> The different ETL pathways differed in reducer choice slightly for -ve hashcodes.
> {code}
> (hashCode & Integer.MAX_VALUE) % numberOfBuckets;
> !=
> Math.abs(hashCode) % numberOfBuckets
> {code}
> Add a backwards compat option, which can be used to protect against old data left over from 0.13.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)