[
https://issues.apache.org/jira/browse/FLINK-35257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17841582#comment-17841582
]
yanghuai edited comment on FLINK-35257 at 12/12/24 6:24 AM:
------------------------------------------------------------
When schema.change.behavior is exception, the task should throw an exception
failure after all downstream data is flushed.
After ddl data is received, the task fails quickly. The data between checkPoint
and ddl is lost
was (Author: yanghuai):
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)
