You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2018/05/04 07:26:00 UTC
[jira] [Updated] (KYLIN-3352) Segment pruning bug, e.g. date_col >
"max_date+1"
[ https://issues.apache.org/jira/browse/KYLIN-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shaofeng SHI updated KYLIN-3352:
--------------------------------
Affects Version/s: v2.1.0
v2.2.0
v2.3.0
Fix Version/s: v2.4.0
> Segment pruning bug, e.g. date_col > "max_date+1"
> -------------------------------------------------
>
> Key: KYLIN-3352
> URL: https://issues.apache.org/jira/browse/KYLIN-3352
> Project: Kylin
> Issue Type: Bug
> Affects Versions: v2.1.0, v2.2.0, v2.3.0
> Reporter: liyang
> Assignee: liyang
> Priority: Major
> Fix For: v2.4.0
>
>
> Currently {{date_col > "max_date+1"}} is rounded down to {{date_col > "max_date"}} during encoding and further evaluated as {{date_col >= "max_date"}} during segment pruning. This causes a segment can be pruned is not pruned.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)