[
https://issues.apache.org/jira/browse/FLINK-31951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31951:
-----------------------------------
Labels: pull-request-available stale-assigned (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> 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
> Assignee: Kevin Tseng
> Priority: Minor
> Labels: pull-request-available, stale-assigned
>
> 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)
