[
https://issues.apache.org/jira/browse/FLINK-20379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20379:
-----------------------------------
Labels: auto-unassigned pull-request-available stale-critical (was:
auto-unassigned 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 issues has been marked as
Critical but is unassigned and neither itself nor its Sub-Tasks have been
updated for 7 days. I have gone ahead and marked it "stale-critical". If this
ticket is critical, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be
deprioritized.
> 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: Critical
> Labels: auto-unassigned, pull-request-available, stale-critical
> Fix For: 1.14.0, 1.12.5
>
>
> 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)
