[
https://issues.apache.org/jira/browse/CALCITE-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhen Chen resolved CALCITE-7357.
--------------------------------
Resolution: Fixed
Fixed in
[{{c3d49bd}}|https://github.com/apache/calcite/commit/c3d49bd4f8a5d0c56fc19a5d2dd1255486221a28]
Thanks for review [~dongsl] [~mbudiu]
> Introduce the implementation of rex operator IS DISTINCT FROM
> --------------------------------------------------------------
>
> Key: CALCITE-7357
> URL: https://issues.apache.org/jira/browse/CALCITE-7357
> Project: Calcite
> Issue Type: New Feature
> Components: core
> Reporter: Zhen Chen
> Assignee: Zhen Chen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.42.0
>
>
> Because testing the new disassociate statement involves executing `IS
> DISTINCT FROM` in SQL, the current `IS DISTINCT FROM` will be rewritten as
> `(x IS NOT NULL OR y IS NOT NULL) AND (x = y) IS NOT TRUE`, so the actual
> execution implementation is not needed. This presents a good opportunity to
> complete this implementation.
>
> When I test join.iq using the CALCITE-7315 PR, I get the following error.
> Suppressed: java.lang.RuntimeException: cannot translate call IS DISTINCT
> FROM($t1, $t3)
> > at
> > org.apache.calcite.adapter.enumerable.RexToLixTranslator.visitCall(RexToLixTranslator.java:1481)
> > at
> > org.apache.calcite.adapter.enumerable.RexToLixTranslator.visitCall(RexToLixTranslator.java:110)
> > at org.apache.calcite.rex.RexCall.accept(RexCall.java:208)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
