[
https://issues.apache.org/jira/browse/FLINK-35128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840657#comment-17840657
]
Qingsheng Ren edited comment on FLINK-35128 at 4/26/24 3:30 AM:
----------------------------------------------------------------
flink-cdc master: bdca0e328bce0aa2dc05153bc67da4c4875586fd
flink-cdc release-3.1: aa2ffd9c2747cde21d09305c2852debb8937b1fb
was (Author: renqs):
flink-cdc master: bdca0e328bce0aa2dc05153bc67da4c4875586fd
> 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: 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)