flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rong Rong (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLINK-7137) Flink table API defaults top level fields as nullable and all nested fields within CompositeType as non-nullable
Date Fri, 07 Jul 2017 23:51:00 GMT
Rong Rong created FLINK-7137:
--------------------------------

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

Mime
View raw message