Mailing-List: contact dev-help@kylin.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kylin.apache.org
Date: Mon, 22 May 2017 06:26:04 +0000 (UTC)
From: "hongbin ma (JIRA)" <jira@apache.org>
To: dev@kylin.apache.org
Message-ID: <JIRA.13073771.1495434341000.260255.1495434364036@Atlassian.JIRA>
In-Reply-To: <JIRA.13073771.1495434341000@Atlassian.JIRA>
References: <JIRA.13073771.1495434341000@Atlassian.JIRA> <JIRA.13073771.1495434341837@jira-lw-us.apache.org>
Subject: [jira] [Created] (KYLIN-2635) optimize determined case when filters
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 22 May 2017 06:26:07 -0000

hongbin ma created KYLIN-2635:
---------------------------------

             Summary: optimize determined case when filters 
                 Key: KYLIN-2635
                 URL: https://issues.apache.org/jira/browse/KYLIN-2635
             Project: Kylin
          Issue Type: Bug
            Reporter: hongbin ma
            Assignee: hongbin ma


currently calcite will not handle with determined filter like:

1. where 1 = 1 => where true
2. where ( 1= 1 or x = 2)  => where true
3. where case when 'a' = 'a' then x > 1 else x < 1 => where x > 1

the first two cases have been handled in KYLIN-2539, however the third case is not handled yet. This JIRA is to track the third case.

In theory, this JIRA together with KYLIN-2539, KYLIN-2597 should be solved in calcite rather than KYLIN. However it's urgent demand so we'll fix in KYLIN first.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)