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

Posted to issues@calcite.apache.org by "Yuzhao Chen (JIRA)" <ji...@apache.org> on 2018/08/08 04:18:00 UTC

[jira] [Commented] (CALCITE-2455) Fix simplifyCoalesce of constant when nullability missing

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

Yuzhao Chen commented on CALCITE-2455:
--------------------------------------

Hi [~julianhyde]

I have fired a PR: https://github.com/apache/calcite/pull/782

> Fix simplifyCoalesce of constant when nullability missing
> ---------------------------------------------------------
>
>                 Key: CALCITE-2455
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2455
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.17.0
>            Reporter: Yuzhao Chen
>            Assignee: Julian Hyde
>            Priority: Major
>             Fix For: 1.18.0
>
>
> After CALCITE-2227, we will not replace Coalesce to Case When for natural join, when we use ReduceExpressionRule for our plan for Coalesce with constant, the nullability will chage( from nullable to notnull), this will cause VolcanoPlanner to throw error.
> Should i fix this? or we should not use this rule in VolcanoPlanner?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)