[
https://issues.apache.org/jira/browse/FLINK-25686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zili Chen closed FLINK-25686.
-----------------------------
Fix Version/s: pulsar-4.0.0
Resolution: Fixed
master via https://github.com/apache/flink-connector-pulsar/pull/12
> Support Pulsar Schema evolution in Pulsar Source Connector
> ----------------------------------------------------------
>
> Key: FLINK-25686
> URL: https://issues.apache.org/jira/browse/FLINK-25686
> Project: Flink
> Issue Type: New Feature
> Components: Connectors / Pulsar
> Reporter: Yufei Zhang
> Assignee: Yufan Sheng
> Priority: Minor
> Labels: Pulsar, pull-request-available, stale-assigned
> Fix For: pulsar-4.0.0
>
>
> Currently the source connector reads all messages as Message<byte[]>, and
> implements a deserialization abstraction to deserialize the byte array
> message. This deserialization abstraction supports both flink schema and
> pulsar schema. However because of this extra layer of abstraction, even when
> using pulsar schema, the schema info is not provided to the consumer
> (client), so it is not using any pulsar’s schema validation mechanism. (If
> pulsar client has a schema, it will send the schema to broker on connect and
> broker will validate if it is a valid schema according to a preset
> compatibility rule :[
> https://pulsar.apache.org/docs/en/schema-evolution-compatibility/|https://pulsar.apache.org/docs/en/schema-evolution-compatibility/]).
> we need to support this schema evolution
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
