[
https://issues.apache.org/jira/browse/KYLIN-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17135410#comment-17135410
]
ASF GitHub Bot commented on KYLIN-4352:
---------------------------------------
zhangayqian commented on pull request #1241:
URL: https://github.com/apache/kylin/pull/1241#issuecomment-643905470
## Summary
- Future segments will not cause query result errors.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> A empty segment will cause incomplete query result in Realtime OLAP
> -------------------------------------------------------------------
>
> Key: KYLIN-4352
> URL: https://issues.apache.org/jira/browse/KYLIN-4352
> Project: Kylin
> Issue Type: Bug
> Components: Real-time Streaming
> Affects Versions: v3.0.0
> Reporter: Xiaoxiang Yu
> Assignee: Xiaoxiang Yu
> Priority: Major
> Labels: document-required
> Fix For: v3.1.0
>
>
> When you query hit a streaming cube, you query will divided into two part,
> one historical part, one realtime part.
> The boundary of two part is decided by the latest READY segment's *End Time*
> . But when you have a segment which segment range is from future(created by
> mistake), it will cause all following query get incomplete result.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
