You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/05/06 10:37:00 UTC
[jira] [Updated] (FLINK-35243) Carry pre-schema payload with SchemaChangeEvents
[ https://issues.apache.org/jira/browse/FLINK-35243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-35243:
-----------------------------------
Labels: pull-request-available (was: )
> Carry pre-schema payload with SchemaChangeEvents
> ------------------------------------------------
>
> Key: FLINK-35243
> URL: https://issues.apache.org/jira/browse/FLINK-35243
> Project: Flink
> Issue Type: Improvement
> Components: Flink CDC
> Reporter: yux
> Priority: Major
> Labels: pull-request-available
> Fix For: cdc-3.2.0
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Currently, Flink CDC 3.x SchemaChangeEvent provides no information about the previous schema state before applying changes.
> Most pipeline sources can't provide PreSchema info (because it's not recorded in the binlog / oplog / ...), but some pipeline sinks require it to perform validation checks and apply schema change. This ticket suggests adding framework-level support to filling pre-schema payload to any SchemaChangeEvent that requires such info.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)