[jira] [Commented] (KYLIN-599) Near real-time support

["liyang (JIRA)" <ji...@apache.org>]

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

liyang commented on KYLIN-599:
------------------------------

The storm decision is left up to user. All Kylin expects is record input that satisfies predefined table schema. User is free to decide to pre-aggregate the input use any streaming processor like storm.

Kylin don't do ETL, that includes any streaming processing.

> Near real-time support
> ----------------------
>
>                 Key: KYLIN-599
>                 URL: https://issues.apache.org/jira/browse/KYLIN-599
>             Project: Kylin
>          Issue Type: New Feature
>          Components: General
>            Reporter: liyang
>            Assignee: liyang
>             Fix For: v0.7.2
>
>         Attachments: Kylin 0.7.x March.pdf
>
>
> (From Jiang Xu in dev mailing list)
> 1. Kafka + storm will build inverted index in memory.  These index will be inserted into hbase by batch (e.g. every 5 minutes).
> 2. The inverted index in hbase will keep the short term data (e.g. 7 days). These index will be converted into data cube by batch (e.g. every 7 day).
> 3. The data cube in hbase will keep the long term data.
> 4. Query engine will decide to use inverted index or data cube in hbase by time range. In future, the query engine can also use the in-memory inverted index in storm that can reduce the data latency from minutes to seconds.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)