You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Konstantin Knauf (Jira)" <ji...@apache.org> on 2021/07/29 07:36:09 UTC
[jira] [Updated] (FLINK-10525) Deserialization schema, skip data,
that couldn't be properly deserialized
[ https://issues.apache.org/jira/browse/FLINK-10525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Knauf updated FLINK-10525:
-------------------------------------
Labels: (was: auto-closed)
Priority: Not a Priority (was: Minor)
> 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: API / Type Serialization System
> Reporter: Rinat Sharipov
> Priority: Not a Priority
>
> 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
(v8.3.4#803005)