[
https://issues.apache.org/jira/browse/FLINK-34436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837148#comment-17837148
]
Yufan Sheng commented on FLINK-34436:
-------------------------------------
If you want to consume all the messages with different types from the same
topic, the GenericRecordDeserializationSchema may be the best approach to use.
https://github.com/apache/flink-connector-pulsar/blob/main/flink-connector-pulsar/src/main/java/org/apache/flink/connector/pulsar/source/reader/deserializer/GenericRecordDeserializationSchema.java
> Avro schema evolution and compatibility issues in Pulsar connector
> ------------------------------------------------------------------
>
> Key: FLINK-34436
> URL: https://issues.apache.org/jira/browse/FLINK-34436
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
> Affects Versions: 1.17.2
> Reporter: Jacek Wislicki
> Priority: Major
>
> We noticed a couple of critical issues in the Pulsar-Flink connector related
> to schema evolution and compatibility. Please see the MRE available at
> https://github.com/JacekWislicki/test11. More details are in the project's
> README file, here is the summary:
> Library versions:
> * Pulsar 3.0.1
> * Flink 1.17.2
> * Pulsar-Flink connector 4.1.0-1.17
> Problems:
> * Exception thrown when schema's fields are added/removed
> * Avro's enum default value is ignored, instead the last known applied
> I believe that I observed the same behaviour in the Pulsar itself, still now
> we are focusing on the connector, hence I was able to document the problems
> when using it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
