From 609b848983ef344c691f7b735115c19e8b5731dc Mon Sep 17 00:00:00 2001 From: houfaxin Date: Tue, 23 Sep 2025 10:37:14 +0800 Subject: [PATCH 1/4] Update tidb-cloud-release-notes.md --- tidb-cloud/tidb-cloud-release-notes.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/tidb-cloud/tidb-cloud-release-notes.md b/tidb-cloud/tidb-cloud-release-notes.md index bd0ff615c3480..86932864d3bfe 100644 --- a/tidb-cloud/tidb-cloud-release-notes.md +++ b/tidb-cloud/tidb-cloud-release-notes.md @@ -8,6 +8,24 @@ aliases: ['/tidbcloud/supported-tidb-versions','/tidbcloud/release-notes'] This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-cloud/) in 2025. +## September 23, 2025 + +**General changes** + +- **TiDB Cloud Dedicated** + + - Support user-controlled splitting of `UPDATE` events in [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) changefeeds. + + In TiDB Cloud Dedicated clusters, you can configure whether to keep `UPDATE` events as raw events or split them into separate `DELETE` and `INSERT` events. This feature provides greater flexibility for advanced replication scenarios. + + This feature is supported only for non-SQL destinations such as Kafka and S3. + + For more information, see [Split primary or unique key `UPDATE` events for non-MySQL sinks](https://docs.pingcap.com/tidb/stable/ticdc-split-update-behavior/#split-primary-or-unique-key-update-events-for-non-mysql-sinks). + + - Provide a new node size for TiDB Cloud Dedicated clusters hosted on Google Cloud-:32 vCPU, 64 GiB. + + This new node size is available for TiDB nodes. + ## September 16, 2025 **General changes** From 6345407e0beac5b03a68a009ac99232bc03d1e23 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Tue, 23 Sep 2025 10:48:57 +0800 Subject: [PATCH 2/4] Apply suggestions from code review Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --- tidb-cloud/tidb-cloud-release-notes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tidb-cloud/tidb-cloud-release-notes.md b/tidb-cloud/tidb-cloud-release-notes.md index 86932864d3bfe..b017025d7b5fd 100644 --- a/tidb-cloud/tidb-cloud-release-notes.md +++ b/tidb-cloud/tidb-cloud-release-notes.md @@ -16,13 +16,13 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c - Support user-controlled splitting of `UPDATE` events in [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) changefeeds. - In TiDB Cloud Dedicated clusters, you can configure whether to keep `UPDATE` events as raw events or split them into separate `DELETE` and `INSERT` events. This feature provides greater flexibility for advanced replication scenarios. + In TiDB Cloud Dedicated clusters, you can configure whether to keep `UPDATE` events as raw events or split them into separate `DELETE` and `INSERT` events. This feature provides greater flexibility for advanced replication scenarios. This feature is supported only for non-SQL destinations such as Kafka and S3. For more information, see [Split primary or unique key `UPDATE` events for non-MySQL sinks](https://docs.pingcap.com/tidb/stable/ticdc-split-update-behavior/#split-primary-or-unique-key-update-events-for-non-mysql-sinks). - - Provide a new node size for TiDB Cloud Dedicated clusters hosted on Google Cloud-:32 vCPU, 64 GiB. + - Provide a new node size for TiDB Cloud Dedicated clusters hosted on Google Cloud: 32 vCPU, 64 GiB. This new node size is available for TiDB nodes. From 1a437a79415ae3dd95854c4d5be2ad541d9195ee Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Tue, 23 Sep 2025 10:49:54 +0800 Subject: [PATCH 3/4] Update tidb-cloud/tidb-cloud-release-notes.md --- tidb-cloud/tidb-cloud-release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/tidb-cloud-release-notes.md b/tidb-cloud/tidb-cloud-release-notes.md index b017025d7b5fd..582a51f6643a8 100644 --- a/tidb-cloud/tidb-cloud-release-notes.md +++ b/tidb-cloud/tidb-cloud-release-notes.md @@ -22,7 +22,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c For more information, see [Split primary or unique key `UPDATE` events for non-MySQL sinks](https://docs.pingcap.com/tidb/stable/ticdc-split-update-behavior/#split-primary-or-unique-key-update-events-for-non-mysql-sinks). - - Provide a new node size for TiDB Cloud Dedicated clusters hosted on Google Cloud: 32 vCPU, 64 GiB. + - Provide a new node size for TiDB Cloud Dedicated clusters hosted on Google Cloud: `32 vCPU, 64 GiB`. This new node size is available for TiDB nodes. From f99dc97c275c03e9f5973df05bd5c158e4c56e58 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Tue, 23 Sep 2025 12:18:33 +0800 Subject: [PATCH 4/4] Apply suggestions from code review Co-authored-by: Grace Cai --- tidb-cloud/tidb-cloud-release-notes.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/tidb-cloud-release-notes.md b/tidb-cloud/tidb-cloud-release-notes.md index 582a51f6643a8..2c55914be532f 100644 --- a/tidb-cloud/tidb-cloud-release-notes.md +++ b/tidb-cloud/tidb-cloud-release-notes.md @@ -18,11 +18,11 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c In TiDB Cloud Dedicated clusters, you can configure whether to keep `UPDATE` events as raw events or split them into separate `DELETE` and `INSERT` events. This feature provides greater flexibility for advanced replication scenarios. - This feature is supported only for non-SQL destinations such as Kafka and S3. + This feature is supported only for non-SQL destinations such as Apache Kafka and Amazon S3. For more information, see [Sink to Apache Kafka](/tidb-cloud/changefeed-sink-to-apache-kafka.md), [Sink to Apache Pulsar](/tidb-cloud/changefeed-sink-to-apache-pulsar.md), and [Sink to Cloud Storage](/tidb-cloud/changefeed-sink-to-cloud-storage.md). - For more information, see [Split primary or unique key `UPDATE` events for non-MySQL sinks](https://docs.pingcap.com/tidb/stable/ticdc-split-update-behavior/#split-primary-or-unique-key-update-events-for-non-mysql-sinks). + For more information about the splitting behavior, see [Split primary or unique key `UPDATE` events for non-MySQL sinks](https://docs.pingcap.com/tidb/stable/ticdc-split-update-behavior/#split-primary-or-unique-key-update-events-for-non-mysql-sinks). - - Provide a new node size for TiDB Cloud Dedicated clusters hosted on Google Cloud: `32 vCPU, 64 GiB`. + - Provide a new node size for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters hosted on Google Cloud: `32 vCPU, 64 GiB`. This new node size is available for TiDB nodes.