flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rafi Aroch (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (FLINK-10525) Deserialization schema, skip data, that couldn't be properly deserialized
Date Wed, 10 Oct 2018 16:48:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-10525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rafi Aroch reassigned FLINK-10525:
----------------------------------

    Assignee: Rafi Aroch

> Deserialization schema, skip data, that couldn't be properly deserialized
> -------------------------------------------------------------------------
>
>                 Key: FLINK-10525
>                 URL: https://issues.apache.org/jira/browse/FLINK-10525
>             Project: Flink
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Rinat Sharipov
>            Assignee: Rafi Aroch
>            Priority: Minor
>
> Hi mates, in accordance with the contract of *org.apache.flink.api.common.serialization.DeserializationSchema*,
it should return *null* value, when content couldn’t be deserialized.
> But in most cases (e.x. *org.apache.flink.formats.avro.AvroDeserializationSchema*) method
fails, if data doesn't satisfy expected schema. 
>   
>  We’ve implemented our own SerDe class, that returns *null*, if data doesn’t satisfy
schema, but it’s rather hard to maintain this functionality during migration to the latest
Flink version. 
> I think, that it’ll be useful feature, if Flink will support optional skip of failed
records in avro and other Deserializers



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message