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

Posted to issues@flink.apache.org by "Leonard Xu (Jira)" <ji...@apache.org> on 2025/04/24 06:24:00 UTC

[jira] [Assigned] (FLINK-37713) SchemaManager was recreated in SchemaRegistry after job failover

     [ https://issues.apache.org/jira/browse/FLINK-37713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leonard Xu reassigned FLINK-37713:
----------------------------------

    Assignee: Yanquan Lv

> SchemaManager was recreated in SchemaRegistry after job failover 
> -----------------------------------------------------------------
>
>                 Key: FLINK-37713
>                 URL: https://issues.apache.org/jira/browse/FLINK-37713
>             Project: Flink
>          Issue Type: Bug
>          Components: Flink CDC
>    Affects Versions: cdc-3.4.0
>            Reporter: Yanquan Lv
>            Assignee: Yanquan Lv
>            Priority: Critical
>              Labels: pull-request-available
>
> OperatorCoordinator#resetToCheckpoint() is called even before OperatorCoordinator#start(), so that SchemaManager was recreated in SchemaRegistry after job failover. 
> This will result in the loss of previously maintained schema information after restarting the job, leading to abnormal schema inference.



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