Details
-
Bug
-
Status: Reopened
-
Minor
-
Resolution: Unresolved
-
1.17.0, 1.18.0
Description
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
AvroDeserializationSchema.deserialize
handles exception, and how
AvroDeserializationSchema.checkAvroInitialized
handles initialization of Decoder object
Attachments
Issue Links
- links to