[
https://issues.apache.org/jira/browse/CALCITE-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038280#comment-17038280
]
Chunwei Lei commented on CALCITE-3803:
--------------------------------------
But I sill don't get Why introducing the {{not (a>1)}} predicate will lead to
incorrect results. At least, I could not get it from the test case of
CALCITE-3192 . Appreciate it much if you can provide a case.
> Enhance RexSimplify to simplify 'a>1 or (a<3 and b)' to 'a>1 or b' if column
> a is not nullable
> ----------------------------------------------------------------------------------------------
>
> Key: CALCITE-3803
> URL: https://issues.apache.org/jira/browse/CALCITE-3803
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Chunwei Lei
> Assignee: Chunwei Lei
> Priority: Major
>
> For {{a>1 or (a<3 and b)}}, with short-circuit, we know {{a<=1}} if {{a>1}}
> is false when column a is not nullable. Then {{(a<3 and b) can be simplified
> to b}}. Thus, {{a>1 or (a<3 and b)is simplified to a>1 or b.}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
