You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Timo Walther (JIRA)" <ji...@apache.org> on 2017/03/08 15:14:38 UTC

[jira] [Assigned] (FLINK-5177) Improve nullability handling

     [ https://issues.apache.org/jira/browse/FLINK-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timo Walther reassigned FLINK-5177:
-----------------------------------

    Assignee: Timo Walther

> Improve nullability handling 
> -----------------------------
>
>                 Key: FLINK-5177
>                 URL: https://issues.apache.org/jira/browse/FLINK-5177
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API & SQL
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>
> Currently, all fields of the Table API are marked as nullable by default. A lot of null checking could be avoided if we would properly handle nullability. Fields of tuples and POJOs with primitive fields can not be null. Elements of primitive arrays too. It also includes parameters and return types of user-defined scalar, table, and aggregate functions.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)