You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (Jira)" <ji...@apache.org> on 2023/12/01 20:56:00 UTC

[jira] [Commented] (CALCITE-6144) JoinInfo is not aware of the IS NOT DISTINCT FROM operator

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

Julian Hyde commented on CALCITE-6144:
--------------------------------------

Your criticism appears valid. Is there a bug that neatly illustrates the problem (e.g. where an 'IS NOT DISTINCT FROM' condition is incorrectly converted to '=')?

> JoinInfo is not aware of the IS NOT DISTINCT FROM operator
> ----------------------------------------------------------
>
>                 Key: CALCITE-6144
>                 URL: https://issues.apache.org/jira/browse/CALCITE-6144
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.35.0
>            Reporter: Claude Brisson
>            Priority: Minor
>
> A join equi-condition can use either EQUALS or IS NOT DISTINCT FROM operator to compare key columns.
> The JoinInfo class looses this information, and the method JoinInfo.getEquiCondition() always generate a conjunction of equalities, which is erroneous if some of the conditions were initially using IS NOT DISTINCT FROM.
> The JoinInfo class would need to store a vector of booleans (indicating the nulls comparison mode for each key pair) to be able to re-generate the full equi-condition.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)