[jira] [Commented] (CALCITE-1601) DateRangeRules loses OR filters

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

    [ https://issues.apache.org/jira/browse/CALCITE-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895879#comment-15895879 ] 

Julian Hyde commented on CALCITE-1601:
--------------------------------------

I had missed one plan improved by this fix. Fixed in http://git-wip-us.apache.org/repos/asf/calcite/commit/4a3df4ef.

> DateRangeRules loses OR filters
> -------------------------------
>
>                 Key: CALCITE-1601
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1601
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.11.0
>            Reporter: Gian Merlino
>            Assignee: Julian Hyde
>             Fix For: 1.12.0
>
>
> I'm not sure why, but DateRangeRules can lose some filters. For example in this query:
> {code}
> SELECT COUNT(*) FROM druid.foo WHERE EXTRACT(YEAR FROM __time) = 2000 AND EXTRACT(MONTH FROM __time) IN (2, 3, 5)
> {code}
> The filter gets resolved to __time >= 2000-02-01 and __time < 2000-03-01, losing the months "3" and "5". Removing DateRangeRules.FILTER_INSTANCE from the planner's rule set stops this from happening.



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