You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "liyang (JIRA)" <ji...@apache.org> on 2017/01/19 13:49:26 UTC
[jira] [Commented] (KYLIN-2397) CubeSegmentScanner generated
inaccurate
[ https://issues.apache.org/jira/browse/KYLIN-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829959#comment-15829959 ]
liyang commented on KYLIN-2397:
-------------------------------
Should add more UT to CubeScanRangePlanner.
> CubeSegmentScanner generated inaccurate
> ---------------------------------------
>
> Key: KYLIN-2397
> URL: https://issues.apache.org/jira/browse/KYLIN-2397
> Project: Kylin
> Issue Type: Improvement
> Components: Query Engine
> Affects Versions: v1.5.4.1
> Reporter: WangSheng
> Assignee: liyang
> Fix For: Future
>
>
> My project has three segment:
> 20160601000000_20160602000000,
> 20160602000000_20160603000000,
> 20160603000000_20160604000000
> When I used filter condition like this : day>='2016-06-01' and day<'2016-06-02'
> Kylin would generated three CubeSegmentScanner, and each CubeSegmentScanner's GTScanRequest are not empty!
> When I changed filter condition like this : day>='2016-06-01' and day<='2016-06-02'
> Kylin would also generated three CubeSegmentScanner, but the last CubeSegmentScanner's GTScanRequest is empty!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)