hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesus Camacho Rodriguez (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-13403) Make Streaming API not create empty buckets (at least as an option)
Date Wed, 25 May 2016 16:19:13 GMT

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

Jesus Camacho Rodriguez commented on HIVE-13403:
------------------------------------------------

Removing 2.1.0 target. Please feel free to commit to branch-2.1 anyway and fix for 2.1.0 if
this happens before the release.

> Make Streaming API not create empty buckets (at least as an option)
> -------------------------------------------------------------------
>
>                 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: Eugene Koifman
>
> 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)

Mime
View raw message