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

Posted to issues@flink.apache.org by "Qingsheng Ren (Jira)" <ji...@apache.org> on 2024/04/26 03:31:00 UTC

[jira] [Resolved] (FLINK-35128) Re-calculate the starting change log offset after the new table added

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

Qingsheng Ren resolved FLINK-35128.
-----------------------------------
    Fix Version/s: cdc-3.1.0
                       (was: 3.1.0)
       Resolution: Fixed

> Re-calculate the starting change log offset after the new table added
> ---------------------------------------------------------------------
>
>                 Key: FLINK-35128
>                 URL: https://issues.apache.org/jira/browse/FLINK-35128
>             Project: Flink
>          Issue Type: Improvement
>          Components: Flink CDC
>            Reporter: Hongshun Wang
>            Assignee: Hongshun Wang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: cdc-3.1.0
>
>
> In mysql cdc, re-calculate the starting binlog offset after the new table added in MySqlBinlogSplit#appendFinishedSplitInfos, while there lack of same action in StreamSplit#appendFinishedSplitInfos. This will cause data loss if any newly added table snapshot split's highwatermark is smaller.
>  
> Some unstable test problem occurs because of it.



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