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

["nichunen (JIRA)" <ji...@apache.org>]

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

nichunen updated KYLIN-3813:
----------------------------
    Fix Version/s:     (was: v3.0.0)
                   v3.0.0-alpha2

> 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-alpha2
>
>
> 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.
> Sample SQL:
> {code}
> select colA
>        case
>            when (colB = (1 = 1)) = (colC = (1 = 1)) then 'B&C'
>            when (colC = (1 = 1)) = (colD = (1 = 1)) then 'C&D'
>            else 'n/a'
>        end as phase,
>        count(*)
> from T
> where session_date between '2018-08-01' and '2018-08-31'
> group by colA
>        case
>            when (colB = (1 = 1)) = (colC = (1 = 1)) then 'B&C'
>            when (colC = (1 = 1)) = (colD = (1 = 1)) then 'C&D'
>            else 'n/a'
>        end;
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)