You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Eugene Koifman (JIRA)" <ji...@apache.org> on 2016/04/08 20:50:25 UTC
[jira] [Updated] (HIVE-11983) Hive streaming API uses incorrect
logic to assign buckets to incoming records
[ https://issues.apache.org/jira/browse/HIVE-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eugene Koifman updated HIVE-11983:
----------------------------------
Fix Version/s: 2.0.0
> Hive streaming API uses incorrect logic to assign buckets to incoming records
> -----------------------------------------------------------------------------
>
> Key: HIVE-11983
> URL: https://issues.apache.org/jira/browse/HIVE-11983
> Project: Hive
> Issue Type: Bug
> Components: HCatalog, Transactions
> Affects Versions: 1.2.1
> Reporter: Roshan Naik
> Assignee: Roshan Naik
> Labels: streaming, streaming_api
> Fix For: 1.3.0, 2.0.0
>
> Attachments: HIVE-11983.3.patch, HIVE-11983.4.patch, HIVE-11983.5.patch, HIVE-11983.patch
>
>
> The Streaming API tries to distribute records evenly into buckets.
> All records in every Transaction that is part of TransactionBatch goes to the same bucket and a new bucket number is chose for each TransactionBatch.
> Fix: API needs to hash each record to determine which bucket it belongs to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)