[
https://issues.apache.org/jira/browse/FLINK-18164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17127562#comment-17127562
]
Benchao Li commented on FLINK-18164:
------------------------------------
[~Leonard Xu] Thanks for the input.
I think it's two different things.
Calcite only takes care the optimization, and the config in calcite will
influence the optimization result.
However, in Flink, we need to take care of the code generation of `EQUALS` and
`NOT_EQUALS`.
> null <> 'str' should be true
> ----------------------------
>
> Key: FLINK-18164
> URL: https://issues.apache.org/jira/browse/FLINK-18164
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API
> Reporter: Benchao Li
> Priority: Major
>
> Currently, if we compare null with other literals, the result will always be
> false.
> It's because the code gen always gives a default value (false) for the
> result. And I think it's a bug if `null <> 'str'` is false.
> It's reported from user-zh:
> http://apache-flink.147419.n8.nabble.com/flink-sql-null-false-td3640.html
> CC [~jark] [~ykt836]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
