ticdc: fix wrong names in bidirectional replication (#21928)

[ti-chi-bot]

This is an automated cherry-pick of #21928

Replaces all instances of 'bi-directional replication' with 'bidirectional replication' across documentation files for consistency. Updates related explanations, configuration references, and limitations to use the unified terminology.

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: fix wrong names in bidirectional replication docs-cn#21008
• 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]

@hfxsd This PR has conflicts, I have hold it.
Please resolve them or ask others to resolve them, then comment /unhold to remove the hold label.

[ti-chi-bot]

@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.

[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 liuxiaozhen12 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 @ti-chi-bot, 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 primarily addresses a documentation consistency issue by standardizing the term "bi-directional replication" to "bidirectional replication" across several files. Beyond this terminology fix, the PR also incorporates a substantial amount of new and updated documentation content, likely as part of a broader cherry-pick or merge from other development branches. This includes significant enhancements to TiCDC's bidirectional replication features (such as DDL replication roles and expanded configuration options), as well as the addition of complete release notes for TiDB 7.6.0 and 8.3.0, and new documentation for TiDB Cloud Recovery Groups. The changes aim to provide clearer and more comprehensive information for users across various TiDB components.

Highlights

• Terminology Standardization: Standardized the term "bi-directional replication" to "bidirectional replication" across various documentation files for consistency.
• TiCDC Bidirectional Replication Enhancements: Introduced new DDL replication roles (PRIMARY, SECONDARY) and expanded limitations within the TiCDC bidirectional replication documentation.
• Expanded TiCDC Changefeed Configurations: Added a comprehensive set of new configuration options for TiCDC changefeeds, covering mounter, filter, scheduler, sink (including CSV, Simple protocol, Kafka, Debezium), consistency (redo log), and integrity settings.
• New Release Notes: Incorporated full release notes for TiDB versions 7.6.0 and 8.3.0, detailing new features, improvements, and bug fixes for these releases.
• TiDB Cloud Recovery Group Documentation: Added new documentation introducing the TiDB Cloud Recovery Group feature, which enables database replication between dedicated clusters for disaster protection.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. ↩

[ti-chi-bot]

@ti-chi-bot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-verify	df0a088	link	true	/test pull-verify

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.

[gemini-code-assist]

Code Review

This pull request aims to standardize the term 'bidirectional replication' across the documentation. While the intent is good, several files contain unresolved merge conflicts, which will break the documentation rendering. I've provided suggestions to fix these conflicts. Please apply them to ensure the documentation is correct and consistent.

[gemini-code-assist]

This section contains unresolved merge conflicts. Please resolve them to ensure the document is rendered correctly. The term bi-directional should also be updated to bidirectional for consistency.

Suggested change

	<<<<<<< HEAD
	Starting from v6.5.0, TiCDC supports bi-directional replication among two TiDB clusters. Based on this feature, you can create a multi-active TiDB solution using TiCDC.
	=======
	TiCDC supports bidirectional replication (BDR) among two TiDB clusters. Based on this feature, you can create a multi-active TiDB solution using TiCDC.
	>>>>>>> 1e9dac24d7 (ticdc: fix wrong names in bidirectional replication (#21928))
	TiCDC supports bidirectional replication (BDR) among two TiDB clusters. Based on this feature, you can create a multi-active TiDB solution using TiCDC.

[gemini-code-assist]

This section contains unresolved merge conflicts. Please resolve them to ensure the document is rendered correctly.

Suggested change

	<<<<<<< HEAD
	After the bidirectional replication is enabled, TiCDC does not replicate any DDL statements. You need to execute DDL statements in the upstream and downstream clusters respectively.
	=======
	Starting from v7.6.0, to support DDL replication as much as possible in bidirectional replication, TiDB divides the [DDLs that TiCDC originally supports](/ticdc/ticdc-ddl.md) into two types: replicable DDLs and non-replicable DDLs, according to the impact of DDLs on the business.
	>>>>>>> 1e9dac24d7 (ticdc: fix wrong names in bidirectional replication (#21928))
	Starting from v7.6.0, to support DDL replication as much as possible in bidirectional replication, TiDB divides the [DDLs that TiCDC originally supports](/ticdc/ticdc-ddl.md) into two types: replicable DDLs and non-replicable DDLs, according to the impact of DDLs on the business.