[
https://issues.apache.org/jira/browse/FLINK-34436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837073#comment-17837073
]
Yufan Sheng commented on FLINK-34436:
-------------------------------------
I think this is not a issue. It's just a design on purpose. The schema
evolution on Pulsar doesn't get proper designed. We just send the desired
schema to Pulsar server and let the validation be performed on server side. The
client side shouldn't perform any validation. Instead, we just use the schema
provided by user for Pub/Sub messages. Sometimes, we even bypass the schema
with pure bytes for (de)serializing messages on flink.
> 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)
