ticdc: update doc about ddl white list #19151
Conversation
|
[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 |
ti-chi-bot
bot
added
missing-translation-status
Co-authored-by: Flowyi <[email protected]>
ticdc/ticdc-ddl.md
Outdated
| - rebase auto id | ||
| - alter table index visibility | ||
| - exchange partition | ||
| - reorganize partition | ||
| - alter table ttl | ||
| - alter table remove ttl | ||
|
|
||
| > ***注意：** |
There was a problem hiding this comment.
这种“注意”的方式很少使用，是需要类似 TiDB 功能概览 | TiDB 文档中心的脚注吗？是的话，可以参考 https://github.com/pingcap/docs-cn/blob/master/basic-features.md 里的格式。
ti-chi-bot
bot
added
size/M
wk989898
changed the title
ticdc/ticdc-ddl.md
Outdated
| > ** 注意：** | ||
| > | ||
| > - 删除最后一个[有效索引](/ticdc/ticdc-overview.md#最佳实践)的 DDL (*号) 不会被同步，并且导致后续数据同步失败。 | ||
| > - 创建第一个[有效索引](/ticdc/ticdc-overview.md#最佳实践)的 DDL (*号) 会被同步，并且导致后续数据同步失败。 |
There was a problem hiding this comment.
这里建议更详细解释一下。比如“在没有有效索引的表创建第一个有效索引的 DDL 会被同步，并且导致后续数据同步失败。 原因是 xxxx”
ti-chi-bot
bot
added
size/L
|
@flowbehappy: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this:
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: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: 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. |
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?