[
https://issues.apache.org/jira/browse/CALCITE-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573891#comment-16573891
]
Julian Hyde commented on CALCITE-2455:
--------------------------------------
A JIRA case should describe the problem, not the solution. Please change the
heading to remove the word "fix".
Also change the git commit message to "[CALCITE-nnn] <jira case description>".
People will correctly assume that it fixes the problem.
> 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)
