[
https://issues.apache.org/jira/browse/FLINK-10525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321556#comment-17321556
]
Flink Jira Bot commented on FLINK-10525:
----------------------------------------
This issue and all of its Sub-Tasks have not been updated for 180 days. So, it
has been labeled "stale-minor". If you are still affected by this bug or are
still interested in this issue, please give an update and remove the label. In
7 days the issue will be closed automatically.
> 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: Minor
> Labels: stale-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
(v8.3.4#803005)
