kylin-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhong Yanghong (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KYLIN-3812) optimize the child CompareTupleFilter in a CompareTupleFilter
Date Wed, 13 Feb 2019 06:23:01 GMT

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

Zhong Yanghong updated KYLIN-3812:
----------------------------------
    Description: 
Currently it's not well supported for CompareTupleFilter to have a child of CompareTupleFilter.
However, in some cases, it's better to support it.
{code}
where (colA = (1=1))
{code}
The *(1=1)* can be transformed to "true". And then this filter can be pushed down to hbase.
Otherwise, the filter *(colA = (1=1))* does not work in hbase.

> optimize the child CompareTupleFilter in a CompareTupleFilter
> -------------------------------------------------------------
>
>                 Key: KYLIN-3812
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3812
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Query Engine
>            Reporter: Zhong Yanghong
>            Assignee: Zhong Yanghong
>            Priority: Major
>
> Currently it's not well supported for CompareTupleFilter to have a child of CompareTupleFilter.
However, in some cases, it's better to support it.
> {code}
> where (colA = (1=1))
> {code}
> The *(1=1)* can be transformed to "true". And then this filter can be pushed down to
hbase. Otherwise, the filter *(colA = (1=1))* does not work in hbase.



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

Mime
View raw message