You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the feature and found no similar feature requirement.
Description
MySQL CDC support start by time.
Currently, the MySQL CDC source supports starting from specific binlog position or GTID. However, in many real-world scenarios, users expect to start a synchronization job based on a human-friendly timestamp, such as:
Resume from "2024-04-01 10:00:00" after failure
Backfill data since a specific time window
Adding support for start-time (e.g. 2024-04-10 08:00:00) will greatly simplify CDC task configuration and make SeaTunnel more user-friendly in operational scenarios.
Search before asking
Description
MySQL CDC support start by time.
Currently, the MySQL CDC source supports starting from specific binlog position or GTID. However, in many real-world scenarios, users expect to start a synchronization job based on a human-friendly timestamp, such as:
Adding support for
start-time
(e.g.2024-04-10 08:00:00
) will greatly simplify CDC task configuration and make SeaTunnel more user-friendly in operational scenarios.Error handling:
User Scenario:
In real-world CDC scenarios, users often face recovery requirements like:
“I want to resume this CDC pipeline from 2024-04-10 00:00:00”
“I want to only capture changes after yesterday 08:00”
“Binlog filename is not available, but timestamp is known”
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: