[jira] [Resolved] (CALCITE-1200) Handle null equality join condition as IS NOT DISTINCT FROM in RelOptUtil.splitJoinCondition

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

     [ https://issues.apache.org/jira/browse/CALCITE-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-1200.
----------------------------------
    Resolution: Fixed

Fixed in http://git-wip-us.apache.org/repos/asf/calcite/commit/3599cebb. Thanks for the PR!

I fixed up a bit, changing getOperator() calls to getKind() for the reasons stated in CALCITE-1043.

> Handle null equality join condition as IS NOT DISTINCT FROM in RelOptUtil.splitJoinCondition
> --------------------------------------------------------------------------------------------
>
>                 Key: CALCITE-1200
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1200
>             Project: Calcite
>          Issue Type: Improvement
>          Components: core
>            Reporter: Venki Korukanti
>            Assignee: Julian Hyde
>             Fix For: 1.8.0
>
>
> Currently {{RelOptUtil.splitJoinCondition}} can't recognize a join condition as equi-join condition if it is given as {{(t1.key = t2.key OR (t1.key IS NULL AND t2.key IS NULL))}} which is basically an expanded version of {{IS NOT DISTINCT FROM}} function.
> This JIRA is to track changes to {{RelOptUtil.splitJoinCondition}} to handle null equality join condition by converting them to {{IS NOT DISTINCT FROM}} function.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)