[
https://issues.apache.org/jira/browse/FLINK-10049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xingcan Cui updated FLINK-10049:
--------------------------------
Description: Currently, the built-in functions treat NULL arguments in
different ways. E.g., ABS(NULL) returns NULL, while LOG10(NULL) throws NPE. The
general SQL-way of handling NULL values should be that if one argument is NULL
the result is NULL. We should keep the correct semantics and avoid terminating
the (continuous) queries unexpectedly. (was: Currently, the built-in functions
treat NULL arguments in different ways. E.g., ABS(NULL) returns NULL, while
LOG10(NULL) throws an NPE. The general SQL-way of handling NULL values should
be that if one argument is NULL the result is NULL. We should unify the
processing logic for that.)
> Correctly handle NULL arguments in SQL built-in functions
> ---------------------------------------------------------
>
> Key: FLINK-10049
> URL: https://issues.apache.org/jira/browse/FLINK-10049
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: Xingcan Cui
> Assignee: vinoyang
> Priority: Major
>
> Currently, the built-in functions treat NULL arguments in different ways.
> E.g., ABS(NULL) returns NULL, while LOG10(NULL) throws NPE. The general
> SQL-way of handling NULL values should be that if one argument is NULL the
> result is NULL. We should keep the correct semantics and avoid terminating
> the (continuous) queries unexpectedly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
