From 14b5f68fb13cae261950855272639c6b83b1f0f0 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Tue, 9 Dec 2025 14:59:27 +0800 Subject: [PATCH 1/5] Add temp.md --- temp.md | 1 + 1 file changed, 1 insertion(+) create mode 100644 temp.md diff --git a/temp.md b/temp.md new file mode 100644 index 0000000000000..af27ff4986a7b --- /dev/null +++ b/temp.md @@ -0,0 +1 @@ +This is a test file. \ No newline at end of file From e0ed5333a84dd6f3824cd295ba0021f5a529579d Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Tue, 9 Dec 2025 14:59:32 +0800 Subject: [PATCH 2/5] Delete temp.md --- temp.md | 1 - 1 file changed, 1 deletion(-) delete mode 100644 temp.md diff --git a/temp.md b/temp.md deleted file mode 100644 index af27ff4986a7b..0000000000000 --- a/temp.md +++ /dev/null @@ -1 +0,0 @@ -This is a test file. \ No newline at end of file From 775586f1ee855d4e46859aefa548f59bb8d58c4e Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Tue, 9 Dec 2025 07:52:23 +0000 Subject: [PATCH 3/5] Auto-sync: Update English docs from Chinese PR Synced from: https://github.com/pingcap/docs-cn/pull/21138 Target PR: https://github.com/pingcap/docs/pull/22161 AI Provider: deepseek Co-authored-by: github-actions[bot] --- ticdc/ticdc-data-replication-capabilities.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/ticdc/ticdc-data-replication-capabilities.md b/ticdc/ticdc-data-replication-capabilities.md index ab67d6338f593..3e147eb671355 100644 --- a/ticdc/ticdc-data-replication-capabilities.md +++ b/ticdc/ticdc-data-replication-capabilities.md @@ -48,3 +48,18 @@ TiCDC supports the following types of upstream data changes: - TiCDC only verifies the integrity of upstream data changes. It does not validate whether the changes conform to upstream or downstream constraints. If the data violates downstream constraints, TiCDC will return an error when writing to the downstream. For example: When a changefeed is configured to filter out all DDL events, if the upstream executes a `DROP COLUMN` operation but continues to write `INSERT` statements involving that column, TiCDC will fail to replicate these DML changes to the downstream because of table schema mismatches. + +- For the TiCDC [classic architecture](/ticdc/ticdc-classic-architecture.md), when the number of tables replicated by a single TiCDC cluster exceeds the following recommended values, TiCDC may not work stably: + + | TiCDC Cluster Version | Recommended Number of Tables to Replicate | + |---|---| + | v5.4.0 - v6.5.x | 2000 | + | v6.5.x - v7.1.x | 4000 | + | v7.5.x - v8.5.x | 40000 | + + > **Note:** + > + > If replicating partitioned tables, TiCDC treats each partition as an independent table. Therefore, the partition count is included when calculating the total number of tables being replicated. + + If the number of tables to replicate exceeds the above recommendations, it is recommended to use the [TiCDC new architecture](/ticdc/ticdc-architecture.md). The new architecture supports replicating over a million tables per changefeed, making it suitable for large-scale replication scenarios. + From d4a47c1818e816464c0392381d8191ada49942b2 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Tue, 9 Dec 2025 16:18:24 +0800 Subject: [PATCH 4/5] Apply suggestions from code review --- ticdc/ticdc-data-replication-capabilities.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ticdc/ticdc-data-replication-capabilities.md b/ticdc/ticdc-data-replication-capabilities.md index 3e147eb671355..c389866dac262 100644 --- a/ticdc/ticdc-data-replication-capabilities.md +++ b/ticdc/ticdc-data-replication-capabilities.md @@ -49,9 +49,9 @@ TiCDC supports the following types of upstream data changes: For example: When a changefeed is configured to filter out all DDL events, if the upstream executes a `DROP COLUMN` operation but continues to write `INSERT` statements involving that column, TiCDC will fail to replicate these DML changes to the downstream because of table schema mismatches. -- For the TiCDC [classic architecture](/ticdc/ticdc-classic-architecture.md), when the number of tables replicated by a single TiCDC cluster exceeds the following recommended values, TiCDC may not work stably: +- For the TiCDC [classic architecture](/ticdc/ticdc-classic-architecture.md), when the number of tables replicated by a single TiCDC cluster exceeds the following recommended values, TiCDC might not work stably: - | TiCDC Cluster Version | Recommended Number of Tables to Replicate | + | TiCDC version | Recommended number of tables to be replicated | |---|---| | v5.4.0 - v6.5.x | 2000 | | v6.5.x - v7.1.x | 4000 | @@ -59,7 +59,7 @@ TiCDC supports the following types of upstream data changes: > **Note:** > - > If replicating partitioned tables, TiCDC treats each partition as an independent table. Therefore, the partition count is included when calculating the total number of tables being replicated. + > When replicating partitioned tables, TiCDC treats each partition as a separate table. Therefore, the partition count is included when TiCDC calculates the total number of tables to be replicated. - If the number of tables to replicate exceeds the above recommendations, it is recommended to use the [TiCDC new architecture](/ticdc/ticdc-architecture.md). The new architecture supports replicating over a million tables per changefeed, making it suitable for large-scale replication scenarios. + If the number of tables to be replicated exceeds the preceding recommended values, it is recommended to use the [TiCDC new architecture](/ticdc/ticdc-architecture.md). The new architecture supports replicating more than one million tables per changefeed, making it suitable for large-scale replication scenarios. From 37dbc7f18ba84a132735b41f7edafb5b578e6df5 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Tue, 9 Dec 2025 16:56:09 +0800 Subject: [PATCH 5/5] Update ticdc/ticdc-data-replication-capabilities.md --- ticdc/ticdc-data-replication-capabilities.md | 1 - 1 file changed, 1 deletion(-) diff --git a/ticdc/ticdc-data-replication-capabilities.md b/ticdc/ticdc-data-replication-capabilities.md index c389866dac262..8c9e8cb0c6d1e 100644 --- a/ticdc/ticdc-data-replication-capabilities.md +++ b/ticdc/ticdc-data-replication-capabilities.md @@ -62,4 +62,3 @@ TiCDC supports the following types of upstream data changes: > When replicating partitioned tables, TiCDC treats each partition as a separate table. Therefore, the partition count is included when TiCDC calculates the total number of tables to be replicated. If the number of tables to be replicated exceeds the preceding recommended values, it is recommended to use the [TiCDC new architecture](/ticdc/ticdc-architecture.md). The new architecture supports replicating more than one million tables per changefeed, making it suitable for large-scale replication scenarios. -