You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Kevin Tseng (Jira)" <ji...@apache.org> on 2023/04/27 04:11:00 UTC
[jira] [Commented] (FLINK-31951) Mix schema record source creates corrupt record
[ https://issues.apache.org/jira/browse/FLINK-31951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716969#comment-17716969 ]
Kevin Tseng commented on FLINK-31951:
-------------------------------------
can a committer assign this bug to me? As this is fairly straightforward and I already have a fix prepared. Thanks!
> Mix schema record source creates corrupt record
> -----------------------------------------------
>
> Key: FLINK-31951
> URL: https://issues.apache.org/jira/browse/FLINK-31951
> Project: Flink
> Issue Type: Bug
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Affects Versions: 1.17.0, 1.18.0
> Reporter: Kevin Tseng
> Priority: Minor
>
> This seems to be an unexpected side effect with how AvroDeserializationSchema class was written.
> Sometimes we do not have control over what record comes through a Kafka Topic.
> In current implementation, if AvroDeserializationSchema encountered a record byte array that does not conform to the specified Schema / SpecificRecord type, it will cause future record to be deserialized incorrectly.
> Origin of the issue is with how
> {code:java}
> AvroDeserializationSchema.deserialize{code}
> handles exception, and how
> {code:java}
> AvroDeserializationSchema.checkAvroInitialized{code}
> handles initialization of Decoder object
--
This message was sent by Atlassian Jira
(v8.20.10#820010)