[
https://issues.apache.org/jira/browse/CALCITE-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711116#comment-17711116
]
Julian Hyde commented on CALCITE-5639:
--------------------------------------
This seems like a more general problem. For example, it's likely that {{NOT
LIKE}}, {{SIMILAR TO}} and {{>}} have this problem. Is there a more general
solution? Is it possible to use {{class Strong}} and deduce that if an operator
returns TRUE then its arguments must all be non-NULL.
Can you make an effort to generalize this before we accept the PR.
> RexSimplify not removes IS NOT NULL check when LIKE comparison is present
> -------------------------------------------------------------------------
>
> Key: CALCITE-5639
> URL: https://issues.apache.org/jira/browse/CALCITE-5639
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.34.0
> Reporter: Leonid Chistov
> Assignee: Leonid Chistov
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Consider query like
> {code:java}
> select r_reason_desc from reason
> where r_reason_desc is not null and r_reason_desc like '%child%'
> {code}
> where "r_reason_desc" is a nullable field.
> When RexSimplify::simplifyFilterPredicates is called on that conjunction of
> expressions, expression is not simplified, meaning that redundant "is not
> null" check is not removed.
> In the same time, if query like
> {code:java}
> select r_reason_desc from reason
> where r_reason_desc is not null and r_reason_desc >= 'A'{code}
> is passed to optimizer, redundant "is not null" check is eliminated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
