Skip to content

docs: clarify TiCDC index DDL ordering (#21829) - #21846

Merged
ti-chi-bot[bot] merged 3 commits into
pingcap:release-8.1from
ti-chi-bot:cherry-pick-21829-to-release-8.1
Jul 29, 2026
Merged

docs: clarify TiCDC index DDL ordering (#21829)#21846
ti-chi-bot[bot] merged 3 commits into
pingcap:release-8.1from
ti-chi-bot:cherry-pick-21829-to-release-8.1

Conversation

@ti-chi-bot

Copy link
Copy Markdown
Member

This is an automated cherry-pick of #21829

First-time contributors' checklist

What is changed, added or deleted? (Required)

  • Clarify in the TiCDC FAQ that the general DML/DDL execution order has an exception for ADD INDEX and CREATE INDEX when the downstream is TiDB.
  • Update the TiCDC DDL page to explicitly call out these two DDLs as exceptions so the FAQ and DDL pages stay consistent.

Which TiDB version(s) do your changes apply to? (Required)

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)

What is the related PR or file link(s)?

AI agent involvement

  • The changes in this PR were primarily made by an AI agent on behalf of the PR author.

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

Summary by CodeRabbit

  • 文档
    • 更新 TiCDC DDL 异步执行说明:在章节中更突出“TiDB 下 ADD INDEX / CREATE INDEX 属于例外”,说明 TiCDC 会在下游同步后立即返回,不等待 DDL 完成以避免阻塞后续 DML。
    • 调整 DML 与 DDL 执行顺序说明:在 如何理解 DML 和 DDL 之间的执行顺序? 中补充 TiDB 场景下 ADD INDEX / CREATE INDEX 的异步例外,并补充相关参考链接。

@ti-chi-bot ti-chi-bot added contribution This PR is from a community contributor. lgtm size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. type/cherry-pick-for-release-8.1 This PR is cherry-picked to release-8.1 from a source PR. labels Jul 29, 2026
@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a42569e2-e788-4608-b1f5-80497450b8cc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@qiancai

qiancai commented Jul 29, 2026

Copy link
Copy Markdown
Collaborator

/approve

@ti-chi-bot

ti-chi-bot Bot commented Jul 29, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiancai

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot Bot added the approved label Jul 29, 2026
@ti-chi-bot
ti-chi-bot Bot merged commit ef482ff into pingcap:release-8.1 Jul 29, 2026
8 checks passed
@ti-chi-bot
ti-chi-bot Bot deleted the cherry-pick-21829-to-release-8.1 branch July 29, 2026 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved contribution This PR is from a community contributor. lgtm size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. type/cherry-pick-for-release-8.1 This PR is cherry-picked to release-8.1 from a source PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants