You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "yanghuai (Jira)" <ji...@apache.org> on 2024/04/28 06:43:00 UTC

[jira] [Commented] (FLINK-35257) optimize the handling of schema.change.behavior as EXCEPTION

    [ https://issues.apache.org/jira/browse/FLINK-35257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17841582#comment-17841582 ] 

yanghuai commented on FLINK-35257:
----------------------------------

if schema.change.behavior is EXCEPTION，just throw exception before com.ververica.cdc.runtime.operators.schema.coordinator.SchemaRegistryRequestHandler#applySchemaChange

> optimize the handling of schema.change.behavior as EXCEPTION
> ------------------------------------------------------------
>
>                 Key: FLINK-35257
>                 URL: https://issues.apache.org/jira/browse/FLINK-35257
>             Project: Flink
>          Issue Type: Improvement
>          Components: Flink CDC
>            Reporter: yanghuai
>            Priority: Major
>
> cdc job will throw exception when schema.change.behavior is exception，The data between the last checkpoint and the current DDL will not be refreshed to the sink, making it difficult for the task to recover this part of the data.
> if the sink will flush all data and then throw an exception. This way, the task only needs to recover from the DDL position on the source to ensure data consistency.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)