You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "François Lacombe (JIRA)" <ji...@apache.org> on 2019/08/01 13:21:00 UTC

[jira] [Created] (FLINK-13536) Improve nullability handling in Types

François Lacombe created FLINK-13536:
----------------------------------------

             Summary: Improve nullability handling in Types
                 Key: FLINK-13536
                 URL: https://issues.apache.org/jira/browse/FLINK-13536
             Project: Flink
          Issue Type: Improvement
          Components: API / Type Serialization System, Formats (JSON, Avro, Parquet, ORC, SequenceFile)
    Affects Versions: 1.8.0
            Reporter: François Lacombe


Currently, Avro to Flink type matching doesn't propagate nullability definition.

In Avro :
{code:java}
"type":["null","string"]{code}
allows Java String myField=null;

while
{code:java}
"type":"string"{code}
doesn't.

It may be good to find corresponding property in Flink types too as to check for nullability in JsonRowDeserializationSchema for instance (null or absent field in parsed JSON should only be possible on nullable fields)

 

Thanks in advance



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)