[jira] [Commented] (FLINK-7137) Flink table API defaults top level fields as nullable and all nested fields within CompositeType as non-nullable

["Fabian Hueske (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-7137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083048#comment-16083048 ] 

Fabian Hueske commented on FLINK-7137:
--------------------------------------

Thanks for reporting this issue.
I don't think this behavior is intended and should be fixed by setting nested fields to nullable as well.

What do you think [~twalthr]?

> Flink table API defaults top level fields as nullable and all nested fields within CompositeType as non-nullable
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-7137
>                 URL: https://issues.apache.org/jira/browse/FLINK-7137
>             Project: Flink
>          Issue Type: Bug
>          Components: Table API & SQL
>    Affects Versions: 1.3.1
>            Reporter: Rong Rong
>
> Right now FlinkTypeFactory does conversion between Flink TypeInformation to Calcite RelDataType by assuming the following: 
> All top level fields will be set to nullable and all nested fields within CompositeRelDataType and GenericRelDataType will be set to Calcite default (which is non-nullable). 
> This triggers Calcite SQL optimization engine drop all `IS NOT NULL` clause on nested fields, and would not be able to optimize when top level fields were actually non-nullable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)