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

Roshan Naik commented on HIVE-5687:
-----------------------------------

[~leftylev] Yes looks like it went unnoticed due to the short time frame. For 
some reason i never got a notification of your review. We can get it in via 
another patch... but it appears to be too late to get it into this release.

[~orahive] You can query the data while it is being streamed into Hive. Queries 
will always see a consistent view of the data as this feature relies on the new 
ACID support in Hive. So queries will not see new data that was committed after 
they began executing. 

FLUME-1734 consumes this API to implement a Flume sink that streams data 
continuously into Hive.

> Streaming support in Hive
> -------------------------
>
>                 Key: HIVE-5687
>                 URL: https://issues.apache.org/jira/browse/HIVE-5687
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Roshan Naik
>            Assignee: Roshan Naik
>              Labels: ACID, Streaming
>             Fix For: 0.13.0
>
>         Attachments: 5687-api-spec4.pdf, 5687-draft-api-spec.pdf, 
> 5687-draft-api-spec2.pdf, 5687-draft-api-spec3.pdf, 
> HIVE-5687-unit-test-fix.patch, HIVE-5687.patch, HIVE-5687.v2.patch, 
> HIVE-5687.v3.patch, HIVE-5687.v4.patch, HIVE-5687.v5.patch, 
> HIVE-5687.v6.patch, HIVE-5687.v7.patch, Hive Streaming Ingest API for v3 
> patch.pdf, Hive Streaming Ingest API for v4 patch.pdf, package.html
>
>
> Implement support for Streaming data into HIVE.
> - Provide a client streaming API 
> - Transaction support: Clients should be able to periodically commit a batch 
> of records atomically
> - Immediate visibility: Records should be immediately visible to queries on 
> commit
> - Should not overload HDFS with too many small files
> Use Cases:
>  - Streaming logs into HIVE via Flume
>  - Streaming results of computations from Storm



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to