[jira] [Created] (KYLIN-4273) Make cube planner works for real-time streaming job

2019-11-28 Thread Gang Ma (Jira) 
Gang Ma created KYLIN-4273:
--

 Summary: Make cube planner works for real-time streaming job
 Key: KYLIN-4273
 URL: https://issues.apache.org/jira/browse/KYLIN-4273
 Project: Kylin
  Issue Type: Improvement
  Components: Real-time Streaming
Reporter: Gang Ma
Assignee: Gang Ma
 Fix For: v3.0.0


Make cube planner works for real-time streaming job:

1, when no ready segment is ready for streaming cube, only 1 segment is allow 
to build, ensure that the 1st phrase cube planner will take effective

2, when there are any optimization job is running, stop new segment building 
for streaming cube



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (KYLIN-4258) Real-time OLAP may return incorrect result for some case

2019-11-16 Thread Gang Ma (Jira) 
Gang Ma created KYLIN-4258:
--

 Summary: Real-time OLAP may return incorrect result for some case
 Key: KYLIN-4258
 URL: https://issues.apache.org/jira/browse/KYLIN-4258
 Project: Kylin
  Issue Type: Improvement
  Components: Real-time Streaming
Affects Versions: v3.0.0-alpha2, v3.0.0-alpha
Reporter: Gang Ma
Assignee: Gang Ma


1. When real-time query group by minute_start and filter by another column, the 
aggregate result maybe not correct, the issue has been addressed in 
[KYLIN-4184|https://issues.apache.org/jira/browse/KYLIN-4184] , the fix is 
good, but in  

NoCompressedColumnReader class, the readBuffer bytes is still shared, it is a 
potential issue, need to be fixed.

2. When filter by a minute_start range, the first minute data may not be 
correct, it is caused 
by:[https://github.com/apache/kylin/blob/master/stream-core/src/main/java/org/apache/kylin/stream/core/storage/columnar/ColumnarSegmentStoreFilesSearcher.java#L68],
 the fragment's max time is inclusive, but this method's max time is exclusive, 
that may skip some fragments for the first minute by mistake.

3. Need to add some UT to cover these two cases.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)