You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Dayue Gao (JIRA)" <ji...@apache.org> on 2017/01/16 07:42:27 UTC

[jira] [Closed] (KYLIN-2399) CubeSegmentScanner generated inaccurate

     [ https://issues.apache.org/jira/browse/KYLIN-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dayue Gao closed KYLIN-2399.
----------------------------
    Resolution: Duplicate

> CubeSegmentScanner generated inaccurate
> ---------------------------------------
>
>                 Key: KYLIN-2399
>                 URL: https://issues.apache.org/jira/browse/KYLIN-2399
>             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)