[
https://issues.apache.org/jira/browse/FLINK-20379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17372548#comment-17372548
]
Jingsong Lee commented on FLINK-20379:
--------------------------------------
It seems that we need to backport this fix to 1.12.6 as well according to
[https://lists.apache.org/thread.html/r8184e5ecee508c8d94bf4102c42c7ecc8a6229aea74b40c3b10635fc%40%3Cdev.flink.apache.org%3E]
> Update KafkaRecordDeserializationSchema to enable reuse of
> DeserializationSchema and KafkaDeserializationSchema
> ---------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-20379
> URL: https://issues.apache.org/jira/browse/FLINK-20379
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
> Affects Versions: 1.12.0
> Reporter: Stephan Ewen
> Priority: Major
> Labels: auto-deprioritized-critical, auto-unassigned,
> pull-request-available
> Fix For: 1.14.0, 1.12.6
>
>
> The new Kafka Connector defines its own deserialization schema and is
> incompatible with the existing library of deserializers.
> That means that users cannot use all of Flink's Formats (Avro, JSON, Csv,
> Protobuf, Confluent Schema Registry, ...) with the new Kafka Connector.
> I think we should change the new Kafka Connector to use the existing
> Deserialization classes, so all formats can be used, and users can reuse
> their deserializer implementations.
> It would also be good to use the existing KafkaDeserializationSchema.
> Otherwise all users need to migrate their sources again.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
