flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7137) Flink table API defaults top level fields as nullable and all nested fields within CompositeType as non-nullable
Date Mon, 24 Jul 2017 10:31:00 GMT

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

ASF GitHub Bot commented on FLINK-7137:
---------------------------------------

Github user twalthr commented on the issue:

    https://github.com/apache/flink/pull/4314
  
    Thanks for the tests @walterddr. I will merge this now...


> 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
>            Assignee: 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)

Mime
View raw message