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 2024/06/03 09:58:00 UTC
[jira] [Updated] (FLINK-35294) Use source config to check if the filter should be applied in timestamp starting mode
[ https://issues.apache.org/jira/browse/FLINK-35294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leonard Xu updated FLINK-35294:
-------------------------------
Fix Version/s: cdc-3.1.1
> 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)