[
https://issues.apache.org/jira/browse/LENS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303057#comment-14303057
]
Amareshwari Sriramadasu commented on LENS-251:
----------------------------------------------
bq. In case of partitioned storage tables, I am presenting what I have
understood about how the update period related info is used during query
execution. Please correct me if I am wrong.
Your understanding is fine.
If i understood right, what we are looking for is a storage table with time
window of availability defined. Sounds it should be fine.
Lets try to answer following questions
# Is knowing the data availability for the window of the storage table
necessary? Is yes, how will user know that data is actually available for the
range he queried Or is not partial Or is not stale. If not, should we mandate
user to choose a time field to know for which time the data is getting answered.
# Do we have to union such data with other tables which are partitioned, for
time range query that is overlapping?
# Do we have to union storage tables with two different windows, for time range
query that is overlapping?
> 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
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
