You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Lefty Leverenz (JIRA)" <ji...@apache.org> on 2016/02/02 12:17: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=15128084#comment-15128084 ]
Lefty Leverenz commented on HIVE-12945:
---------------------------------------
Doc note: This adds *hive.tez.bucket.pruning.compat* to HiveConf.java, so it needs to be documented in the wiki in the Tez section of Configuration Properties. (TODOC2.0 label added.)
* [Configuration Properties -- Tez | https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-Tez]
> 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
> Labels: TODOC2.0
> Fix For: 2.0.0, 2.1.0
>
> Attachments: HIVE-12945.02.patch, 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)