[
https://issues.apache.org/jira/browse/FLINK-10049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814703#comment-16814703
]
Hequn Cheng commented on FLINK-10049:
-------------------------------------
Yes, I meant to unify the logic for the two problems I listed. Whether return
null or throw NPE depends on the detailed logic of UDFs and may vary
differently. What we have to do is to make sure the semantics and try to avoid
exception if null is ok. :-)
+1 to rename the title.
Best, Hequn
> Unify the processing logic for 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 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
