You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Wei Zheng (JIRA)" <ji...@apache.org> on 2016/08/24 23:29:21 UTC
[jira] [Updated] (HIVE-13403) Make Streaming API not create empty
buckets
[ https://issues.apache.org/jira/browse/HIVE-13403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wei Zheng updated HIVE-13403:
-----------------------------
Summary: Make Streaming API not create empty buckets (was: Make Streaming API not create empty buckets (at least as an option))
> Make Streaming API not create empty buckets
> -------------------------------------------
>
> Key: HIVE-13403
> URL: https://issues.apache.org/jira/browse/HIVE-13403
> Project: Hive
> Issue Type: Bug
> Components: HCatalog, Transactions
> Affects Versions: 1.3.0
> Reporter: Eugene Koifman
> Assignee: Wei Zheng
> Priority: Critical
> Attachments: HIVE-13403.1.patch, HIVE-13403.2.patch, HIVE-13403.3.patch, HIVE-13403.4.patch, HIVE-13403.5.patch
>
>
> as of HIVE-11983, when a TransactionBatch is opened in StreamingAPI, a full compliment of bucket files (AbstractRecordWriter.createRecordUpdaters()) is created on disk even though some may end up receiving no data.
> It would be better to create them on demand and not clog the FS.
> Tez can handle missing (empty) buckets and on MR bucket join algorithms will check if all buckets are there and bail out if not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)