ticdc: improve description about ticdc compatibility with lightning & BR

[lidezhu]

First-time contributors' checklist

• I've signed the Contributor License Agreement, which is required for the repository owners to accept my contribution.

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.

• 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)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 versions)

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

• This PR is translated from: ticdc: improve description about ticdc compatibility with lightning & BR docs-cn#20733
• Other reference link(s):

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

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign oreoxmt for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[gemini-code-assist]

Summary of Changes

Hello @lidezhu, I'm Gemini Code Assist¹! 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 significantly enhances the documentation for TiCDC by providing clearer and more detailed information regarding its compatibility with TiDB Lightning's physical import mode and BR (Backup & Restore). The changes aim to prevent common issues like replication stalls or data inconsistencies by guiding users through the correct procedures when these tools are used in conjunction with TiCDC. The updates involve restructuring existing FAQ content into more specific sections and updating relevant cross-references across the documentation.

Highlights

• Clarified TiCDC Compatibility with TiDB Lightning: The documentation now provides a comprehensive explanation of the compatibility limitations and recommended procedures when using TiDB Lightning's physical import mode with TiCDC, detailing how to manage replication tasks to prevent data inconsistencies.
• Detailed BR (Backup & Restore) Compatibility with TiCDC: A new, dedicated section in the FAQ elaborates on the compatibility between BR (Backup & Restore) and TiCDC, including specific behaviors for different BR versions and conditions under which restore operations are allowed.
• Updated Cross-References in Documentation: Cross-references in the ticdc-overview.md and tidb-lightning-physical-import-mode.md files have been updated to direct users to the newly expanded and clarified compatibility information within the TiCDC FAQ.

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

1. 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. ↩

[gemini-code-assist]

Code Review

This pull request significantly improves the documentation by splitting the FAQ on TiCDC's compatibility with TiDB Lightning and BR into two more focused and detailed sections. The changes enhance clarity and make the information easier for users to find. My review includes several suggestions to further refine the text for grammar, clarity, and adherence to the style guide. Key recommendations involve correcting minor grammatical points, rephrasing for better readability, removing a confusing leftover code block, and ensuring consistent formatting for technical terms.

[gemini-code-assist]

The phrasing "do not guarantee the ability to fully capture" is a bit weak and indirect. Using "cannot fully capture" is more direct and clearer for the user.

Suggested change

BR (Backup & Restore) also directly generates SST files and imports them into the TiKV cluster. Changefeeds do not guarantee the ability to fully capture data imported in this manner. For details, refer to [What are the compatibility limitations between TiDB Lightning Physical Import Mode and TiCDC?](/ticdc/ticdc-faq.md#what-are-the-compatibility-limitations-between-tidb-lightning-physical-import-mode-and-ticdc).

BR (Backup & Restore) also directly generates SST files and imports them into the TiKV cluster. Changefeeds cannot fully capture data imported in this manner. For details, refer to [What are the compatibility limitations between TiDB Lightning Physical Import Mode and TiCDC?](/ticdc/ticdc-faq.md#what-are-the-compatibility-limitations-between-tidb-lightning-physical-import-mode-and-ticdc).