-
Notifications
You must be signed in to change notification settings - Fork 293
puller: Support discarding unsupported DDL by setting ignore-txn-start-ts
in filter. (#12287)
#12291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: release-8.1
Are you sure you want to change the base?
puller: Support discarding unsupported DDL by setting ignore-txn-start-ts
in filter. (#12287)
#12291
Conversation
Signed-off-by: ti-chi-bot <[email protected]>
This cherry pick PR is for a release branch and has not yet been approved by triage owners. To merge this cherry pick:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@asddongmen This PR has conflicts, I have hold it. |
@ti-chi-bot: ## If you want to know how to resolve it, please read the guide in TiDB Dev Guide. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @ti-chi-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request introduces a new filtering capability for DDL (Data Definition Language) operations within TiCDC's ddlPuller
. It allows users to explicitly skip or discard DDLs that cannot be handled by TiCDC by specifying their transaction start timestamps (startTs
) in a new ignore-txn-start-ts
filter configuration. This enhancement improves the robustness of changefeeds by providing a mechanism to bypass problematic DDLs and continue replication.
Highlights
- New
ignore-txn-start-ts
Filter Option: A new configurationignore-txn-start-ts
is added to the filter, enabling users to specify a list of transaction start timestamps for DDLs that should be discarded. - Enhanced DDL Discarding Logic: The
ShouldDiscardDDL
function now considers the DDL'sstartTs
in addition to its type, schema, and table name, allowing for more granular control over which DDLs are processed. - Improved Multi-Table DDL Handling: Specific logic has been implemented to correctly handle
CREATE TABLES
DDLs, allowing individual tables within such operations to be discarded if theirstartTs
matches the ignore list, preventing the entire DDL from failing replication. - Robustness for Unhandled DDLs: This feature provides a critical escape hatch for changefeeds encountering DDLs that TiCDC cannot currently process, allowing replication to continue without manual intervention or data loss.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a useful feature to discard DDLs by their transaction start timestamp, which can help in skipping problematic DDLs. The changes to the filter interface and its implementation are logical. However, the file cdc/puller/ddl_puller.go
contains several unresolved merge conflicts. These are critical issues that must be resolved before this pull request can be merged. I have also included a minor suggestion to improve logging.
<<<<<<< HEAD | ||
======= | ||
case timodel.ActionCreateTables: | ||
querys, err := ddl.SplitQueries(job.Query) | ||
if err != nil { | ||
return false, errors.Trace(err) | ||
} | ||
// we only use multiTableInfos and Querys when we generate job event | ||
// So if some table should be discard, we just need to delete the info from multiTableInfos and Querys | ||
if len(querys) != len(job.BinlogInfo.MultipleTableInfos) { | ||
log.Error("the number of queries in `Job.Query` is not equal to "+ | ||
"the number of `TableInfo` in `Job.BinlogInfo.MultipleTableInfos`", | ||
zap.Int("numQueries", len(querys)), | ||
zap.Int("numTableInfos", len(job.BinlogInfo.MultipleTableInfos)), | ||
zap.String("Job.Query", job.Query), | ||
zap.Any("Job.BinlogInfo.MultipleTableInfos", job.BinlogInfo.MultipleTableInfos), | ||
zap.Error(cerror.ErrTiDBUnexpectedJobMeta.GenWithStackByArgs())) | ||
return false, cerror.ErrTiDBUnexpectedJobMeta.GenWithStackByArgs() | ||
} | ||
|
||
var newMultiTableInfos []*timodel.TableInfo | ||
var newQuerys []string | ||
|
||
multiTableInfos := job.BinlogInfo.MultipleTableInfos | ||
|
||
for index, tableInfo := range multiTableInfos { | ||
// judge each table whether need to be skip | ||
if p.filter.ShouldDiscardDDL(job.Type, job.SchemaName, tableInfo.Name.O, job.StartTS) { | ||
continue | ||
} | ||
newMultiTableInfos = append(newMultiTableInfos, multiTableInfos[index]) | ||
newQuerys = append(newQuerys, querys[index]) | ||
} | ||
|
||
skip = len(newMultiTableInfos) == 0 | ||
|
||
job.BinlogInfo.MultipleTableInfos = newMultiTableInfos | ||
job.Query = strings.Join(newQuerys, "") | ||
>>>>>>> db43be26bf (puller: Support discarding unsupported DDL by setting `ignore-txn-start-ts` in filter. (#12287)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<<<<<<< HEAD | ||
shouldDiscardOldTable = p.filter.ShouldDiscardDDL(job.Type, oldSchemaNames[i].O, oldTable.Name.O) | ||
======= | ||
shouldDiscardOldTable = p.filter.ShouldDiscardDDL(job.Type, info.OldSchemaName.O, oldTable.Name.O, job.StartTS) | ||
>>>>>>> db43be26bf (puller: Support discarding unsupported DDL by setting `ignore-txn-start-ts` in filter. (#12287)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<<<<<<< HEAD | ||
shouldDiscardNewTable = p.filter.ShouldDiscardDDL(job.Type, newSchemaName.Name.O, newTableNames[i].O) | ||
======= | ||
shouldDiscardNewTable = p.filter.ShouldDiscardDDL(job.Type, newSchemaName.Name.O, info.NewTableName.O, job.StartTS) | ||
>>>>>>> db43be26bf (puller: Support discarding unsupported DDL by setting `ignore-txn-start-ts` in filter. (#12287)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
skip = len(newMultiTableInfos) == 0 | ||
|
||
job.BinlogInfo.MultipleTableInfos = newMultiTableInfos | ||
job.Query = strings.Join(newQuerys, "") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ti-chi-bot: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
This is an automated cherry-pick of #12287
What problem does this PR solve?
Issue Number: close #12286
What is changed and how it works?
IgnoreTxnStartTs
in the filter configuration. It is also helpful when we need to skip DDLs that cannot be handled by TiCDC.Check List
Tests
cf.toml
, add theignore-txn-start-ts=[460194169353928710]
to filter.cf.toml
.Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note