[ https://issues.apache.org/jira/browse/FLINK-35294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17849615#comment-17849615 ]
Leonard Xu edited comment on FLINK-35294 at 6/3/24 9:58 AM: ------------------------------------------------------------ Implemented via master: bddcaae7846671c0447b2aa6c7d8e96638988f99 3.1: 5650ee29c6afaaa9139f5cddab4d5391e100b7be was (Author: leonard xu): Implemented master via : bddcaae7846671c0447b2aa6c7d8e96638988f99 > Use source config to check if the filter should be applied in timestamp > starting mode > ------------------------------------------------------------------------------------- > > Key: FLINK-35294 > URL: https://issues.apache.org/jira/browse/FLINK-35294 > Project: Flink > Issue Type: Bug > Components: Flink CDC > Affects Versions: cdc-3.1.0 > Reporter: Xiao Huang > Assignee: Xiao Huang > Priority: Major > Labels: pull-request-available > Fix For: cdc-3.2.0, cdc-3.1.1 > > > Since MySQL does not support the ability to quickly locate an binlog offset > through a timestamp, the current logic for starting from a timestamp is to > begin from the earliest binlog offset and then filter out the data before the > user-specified position. > If the user restarts the job during the filtering process, this filter will > become ineffective. -- This message was sent by Atlassian Jira (v8.20.10#820010)