[
https://issues.apache.org/jira/browse/LENS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642646#comment-14642646
]
Sharad Agarwal commented on LENS-251:
-------------------------------------
mvn package -DskipTests=true is passing for me locally:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:26 min
[INFO] Finished at: 2015-07-27T17:45:50+05:30
[INFO] Final Memory: 162M/875M
[INFO] ------------------------------------------------------------------------
~/projects/incubator-lens>git status
# On branch master
nothing to commit (working directory clean)
~/projects/incubator-lens>git describe
apache-lens-2.2.0-beta-incubating-38-g3ce889f
~/projects/incubator-lens>git log
commit 3ce889fcb4c350b4c306c6b84a15b2b21fbba2aa
Author: Rajat Khandelwal <[email protected]>
Date: Mon Jul 27 16:57:28 2015 +0530
> Support to query streaming data sources
> ---------------------------------------
>
> Key: LENS-251
> URL: https://issues.apache.org/jira/browse/LENS-251
> Project: Apache Lens
> Issue Type: New Feature
> Components: cube
> Reporter: Sharad Agarwal
> Assignee: Sharad Agarwal
> Labels: Hackathon-July
> Fix For: 2.3
>
> Attachments: lens-251.1.patch
>
>
> For certain stores that allows streaming ingestion, to make the data
> available immediately for querying, we need the notion of streaming update
> period or some such.
> Describing by example:
> - lets say there are two drivers - D1 and D2.
> - D1 queries storage S1
> - D2 queries storage S2
> S1 and S2 are part of the same Cube.
> In S1 data is in hourly granularity loaded every hour, while S2 has data
> being ingested continuously in streaming fashion and maintains last 5 hours
> window of data.
> Now based on the query time range we want to select the right driver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
