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 2020/03/19 10:20:00 UTC
[jira] [Closed] (FLINK-16344) Preserve nullability for nested types
[ https://issues.apache.org/jira/browse/FLINK-16344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timo Walther closed FLINK-16344.
--------------------------------
Fix Version/s: 1.11.0
Resolution: Fixed
Fixed in 1.11.0: 5ce71d4def3af1e7491cd6075b034710a5da87f0
> Preserve nullability for nested types
> -------------------------------------
>
> Key: FLINK-16344
> URL: https://issues.apache.org/jira/browse/FLINK-16344
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
> Reporter: Timo Walther
> Assignee: Timo Walther
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, FlinkTypeFactory does not always preserve nullability attributes when handling nested types.
> E.g. a table function that returns {{ROW<s STRING, sa ARRAY<STRING> NOT NULL>}} looses information to {{ROW<s STRING, sa ARRAY<STRING>>}}.
> Same for built-in functions such as {{COLLECT}} which results in mismatches as mentioned in FLINK-14042.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)