[
https://issues.apache.org/jira/browse/FLINK-21582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298033#comment-17298033
]
Timo Walther edited comment on FLINK-21582 at 3/9/21, 11:59 AM:
----------------------------------------------------------------
I understand the reasoning behind it but this arbitrary behavior has
consequences that we should address in the mid term. In theory, the behavior
should be configurable. And based on this config flag all type inferences would
behave differently. Or even better: We modify the plan to wrap an nullable
expression around it.
was (Author: twalthr):
I understand the reasoning behind it but this arbitrary behavior has
consequences that we should address in the mid term. In theory, the behavior
should be configurable. And based on this config flag all type inferences would
behave differently.
> COALESCE not works when cast a variable return null
> ---------------------------------------------------
>
> Key: FLINK-21582
> URL: https://issues.apache.org/jira/browse/FLINK-21582
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API
> Affects Versions: 1.11.1
> Environment: Flink1.11.1
>
> Reporter: Jerry
> Priority: Minor
> Attachments: image-2021-03-03-19-48-21-306.png
>
>
> select COALESCE(cast('aa' as int), 0);return NULL
> select COALESCE(NULL, 0); return 0
> The first case works failed, but the second case works successful
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
