[
https://issues.apache.org/jira/browse/FLINK-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-5177:
----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned
(was: auto-deprioritized-major auto-unassigned stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Improve nullability handling
> -----------------------------
>
> Key: FLINK-5177
> URL: https://issues.apache.org/jira/browse/FLINK-5177
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: Timo Walther
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> auto-unassigned
>
> 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
(v8.20.1#820001)
