You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Zhong Yanghong (JIRA)" <ji...@apache.org> on 2019/03/18 03:46:00 UTC

[jira] [Updated] (KYLIN-3813) don't do push down when both of the children of CompareTupleFilter are CompareTupleFilter with column included

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

Zhong Yanghong updated KYLIN-3813:
----------------------------------
    Fix Version/s: v3.0.0

> don't do push down when both of the children of CompareTupleFilter are CompareTupleFilter with column included
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: KYLIN-3813
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3813
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Query Engine
>            Reporter: Zhong Yanghong
>            Assignee: Zhong Yanghong
>            Priority: Major
>             Fix For: v3.0.0
>
>
> When dynamic column is enabled, kylin will try to push down group by case when to hbase. However, in the following case, the push down should not be enabled, since currently it's not well supported for CompareTupleFilter to have a child of CompareTupleFilter.
> {code}
> case when (colA = (1=1)) = (colB = (1=1)) then 'XXX'
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)