cloud: add migration docs for TiDB Cloud Essential #21849

xuanyu66 · 2025-09-30T02:41:32Z

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.

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

This PR is translated from:
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

gemini-code-assist · 2025-09-30T02:41:47Z

Summary of Changes

Hello @xuanyu66, 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 introduces two new essential documentation pages for TiDB Cloud, guiding users through the process of migrating MySQL-compatible databases to TiDB Cloud Essential. The documentation covers detailed steps for both full data migration (existing and incremental) and incremental-only migration, including critical prerequisites like binary log configuration, network setup, and privilege management, aiming to simplify and streamline the migration experience for various cloud and self-managed MySQL environments.

Highlights

New Migration Guide (Full & Incremental): A new document migrate-from-mysql-using-data-migration-essential.md has been added, providing a comprehensive guide for migrating MySQL-compatible databases (including Amazon Aurora MySQL, Amazon RDS, Azure Database for MySQL, Google Cloud SQL for MySQL, and self-managed MySQL) to TiDB Cloud Essential. This guide covers both existing data and continuous incremental replication.
New Migration Guide (Incremental Only): A companion document migrate-incremental-data-from-mysql-using-data-migration-essential.md has been added, specifically detailing the process for migrating only incremental data from MySQL-compatible sources to TiDB Cloud Essential.
Detailed Prerequisites: Both guides include extensive prerequisites, such as supported data sources and versions, binary log configuration for replication (log_bin, binlog_format, binlog_row_image, binlog_expire_logs_seconds), network connectivity setup (public endpoints, private links, TLS/SSL), and necessary user privileges for both source and target databases.
Step-by-Step Migration Process: The documents outline a clear 7-step process for setting up and executing a data migration job, from navigating the TiDB Cloud console to configuring connections, choosing migration types, selecting objects, prechecks, spec selection, and monitoring progress.
Specific Limitations and Troubleshooting: Each guide details specific limitations related to availability, maximum job count, filtered databases, and nuances of existing vs. incremental data migration, along with references to troubleshooting resources for precheck and migration errors.

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.

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 introduces two new documentation files for migrating data to TiDB Cloud Essential clusters. My review focuses on improving clarity, consistency, and adherence to the documentation style guide. The feedback includes correcting links to ensure they point to the appropriate 'Essential' cluster documentation, standardizing terminology for supported data sources and connectivity methods across both documents, fixing minor formatting issues such as non-breaking spaces and hyphens, and enhancing the clarity of several instructions to improve the user experience.

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration-essential.md

tidb-cloud/migrate-from-mysql-using-data-migration-essential.md

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration-essential.md

tidb-cloud/migrate-from-mysql-using-data-migration-essential.md

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration-essential.md

tidb-cloud/migrate-from-mysql-using-data-migration-essential.md

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration-essential.md

tidb-cloud/migrate-from-mysql-using-data-migration-essential.md

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration-essential.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

Copilot

Pull request overview

This PR adds comprehensive documentation for migrating data from MySQL-compatible databases to TiDB Cloud Essential using the Data Migration feature. The documentation covers both full migration (existing + incremental data) and incremental-only migration scenarios.

Changes:

Added a comprehensive guide for migrating both existing and incremental data from MySQL-compatible databases to TiDB Cloud Essential
Added a focused guide for migrating only incremental data from MySQL-compatible databases to TiDB Cloud Essential
Updated the TOC to include the two new migration documents

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 8 comments.

File	Description
`tidb-cloud/migrate-from-mysql-using-data-migration-essential.md`	Main migration guide covering prerequisites, configuration, and step-by-step instructions for migrating existing and incremental data
`tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration-essential.md`	Focused guide for incremental-only data migration with specific limitations and prerequisites
`TOC-tidb-cloud-essential.md`	Added entries for both new migration documents in the table of contents

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration-essential.md

tidb-cloud/migrate-from-mysql-using-data-migration-essential.md

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration-essential.md

ti-chi-bot · 2026-01-13T12:29:45Z

[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 ask for approval from hfxsd. 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.

Details

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

tidb-cloud/migrate-from-mysql-using-data-migration-essential.md

zhangyangyu · 2026-01-19T08:32:29Z

tidb-cloud/migrate-from-mysql-using-data-migration-essential.md

+- During incremental data migration, if the table to be migrated already exists in the target database with duplicate keys, an error is reported and the migration is interrupted. In this situation, you need to verify that the MySQL source data is accurate. If it is, click the **Restart** button of the migration job, and the migration job will replace the conflicting records in the target cluster with the MySQL source records.
+
+- During incremental replication (migrating ongoing changes to your cluster), if the migration job recovers from an abrupt error, it might open the safe mode for 60 seconds. During the safe mode, `INSERT` statements are migrated as `REPLACE`, `UPDATE` statements as `DELETE` and `REPLACE`, and then these transactions are migrated to the target TiDB Cloud cluster to ensure that all the data during the abrupt error has been migrated smoothly to the target TiDB Cloud cluster. In this scenario, for MySQL source tables without primary keys or non-null unique indexes, some data might be duplicated in the target TiDB Cloud cluster because the data might be inserted repeatedly into the target TiDB Cloud cluster.


incremental replication 和 incremental data migration 有区别么？

没有区别吧

tidb-cloud/migrate-from-mysql-using-data-migration-essential.md

pingcap/docs@7aeb8ff

tidb-cloud/migrate-from-mysql-using-data-migration-essential.md

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration-essential.md

Co-authored-by: Grace Cai <[email protected]>

tidb-cloud/migrate-from-mysql-using-data-migration.md

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md

tidb-cloud/migrate-from-mysql-using-data-migration.md

Co-authored-by: Grace Cai <[email protected]>

tidb-cloud/migrate-from-mysql-using-data-migration.md

qiancai · 2026-01-19T09:44:14Z

tidb-cloud/migrate-from-mysql-using-data-migration.md

+        </CustomContent>
+        <CustomContent plan="essential">
+
+        - If **Public IP** is selected, fill in the **Hostname or IP address** field with the hostname or IP address of the data source.


Suggested change

- If **Public IP** is selected, fill in the **Hostname or IP address** field with the hostname or IP address of the data source.

- If **Public** is selected, fill in the **Hostname or IP address** field with the hostname or IP address of the data source.

qiancai · 2026-01-19T09:57:58Z

tidb-cloud/migrate-from-mysql-using-data-migration.md

 ### Availability

- The Data Migration feature is available only for **TiDB Cloud Dedicated** clusters.
+- Currently, the Data Migration features is not available for {{{ .starter }}}.


Suggested change

- Currently, the Data Migration features is not available for {{{ .starter }}}.

- Currently, the Data Migration feature is not available for {{{ .starter }}}.

qiancai · 2026-01-19T09:58:44Z

tidb-cloud/migrate-from-mysql-using-data-migration.md

+
+4. After applying the changes (and restarting if needed), connect to the instance and run the `SHOW VARIABLES` statement in this section to verify the configuration.
+
+For detailed instructions, see [Set instance parameters](https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-mysql/modify-the-parameters-of-an-apsaradb-rds-for-mysql-instance)


Suggested change

For detailed instructions, see [Set instance parameters](https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-mysql/modify-the-parameters-of-an-apsaradb-rds-for-mysql-instance)

For more information, see [Set instance parameters](https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-mysql/modify-the-parameters-of-an-apsaradb-rds-for-mysql-instance).

qiancai · 2026-01-19T09:59:14Z

tidb-cloud/migrate-from-mysql-using-data-migration.md

 > The egress IP range for your firewall is available only during Data Migration task creation. You cannot obtain this IP range in advance. Before you begin, ensure that you:
 >
 > - Have permissions to modify firewall rules.
 > - Can access to your cloud provider's console during the setup process.


Suggested change

> - Can access to your cloud provider's console during the setup process.

> - Can access your cloud provider's console during the setup process.

qiancai · 2026-01-19T10:00:22Z

tidb-cloud/migrate-from-mysql-using-data-migration.md


 ## Step 5: Precheck

 On the **Precheck** page, you can view the precheck results. If the precheck fails, you need to operate according to **Failed** or **Warning** details, and then click **Check again** to recheck.


Suggested change

On the **Precheck** page, you can view the precheck results. If the precheck fails, you need to operate according to **Failed** or **Warning** details, and then click **Check again** to recheck.

On the **Precheck** page, you can view the precheck results. If the precheck fails, you need to resolve the issues according to the **Failed** or **Warning** details, and then click **Check again** to recheck.

hfxsd · 2026-01-19T14:22:10Z

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md

   - **Data source**: the data source type.
   - **Region**: the region of the data source, which is required for cloud databases only.


Suggested change

- **Data source**: the data source type.

- **Region**: the region of the data source, which is required for cloud databases only.

- **Data source**: the data source type.

- **Region**: the region of the data source, which is required for cloud databases only.

hfxsd · 2026-01-19T14:22:26Z

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md

+   - **Connectivity method**: the connection method for the data source. <CustomContent plan="dedicated">Currently, you can choose public IP, VPC Peering, or Private Link according to your connection method.</CustomContent><CustomContent plan="essential">You can choose public IP or Private Link according to your connection method.</CustomContent>
+
+   <CustomContent plan="dedicated">


Suggested change

- **Connectivity method**: the connection method for the data source. <CustomContent plan="dedicated">Currently, you can choose public IP, VPC Peering, or Private Link according to your connection method.</CustomContent><CustomContent plan="essential">You can choose public IP or Private Link according to your connection method.</CustomContent>

<CustomContent plan="dedicated">

- **Connectivity method**: the connection method for the data source. <CustomContent plan="dedicated">Currently, you can choose public IP, VPC Peering, or Private Link according to your connection method.</CustomContent><CustomContent plan="essential">You can choose public IP or Private Link according to your connection method.</CustomContent>

<CustomContent plan="dedicated">

hfxsd · 2026-01-19T14:22:39Z

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md

   - **Hostname or IP address** (for public IP and VPC Peering): the hostname or IP address of the data source.
   - **Service Name** (for Private Link): the endpoint service name.


Suggested change

- **Hostname or IP address** (for public IP and VPC Peering): the hostname or IP address of the data source.

- **Service Name** (for Private Link): the endpoint service name.

- **Hostname or IP address** (for public IP and VPC Peering): the hostname or IP address of the data source.

- **Service Name** (for Private Link): the endpoint service name.

hfxsd · 2026-01-19T14:22:49Z

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md

+   </CustomContent>
+   <CustomContent plan="essential">


Suggested change

</CustomContent>

<CustomContent plan="essential">

</CustomContent>

<CustomContent plan="essential">

hfxsd · 2026-01-19T14:22:58Z

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md

+   - **Hostname or IP address** (for public IP): the hostname or IP address of the data source.
+   - **Private Link Connection** (for Private Link): the private link connection that you created in the [Private Link Connections](/tidb-cloud/serverless-private-link-connection.md) section.


Suggested change

- **Hostname or IP address** (for public IP): the hostname or IP address of the data source.

- **Private Link Connection** (for Private Link): the private link connection that you created in the [Private Link Connections](/tidb-cloud/serverless-private-link-connection.md) section.

- **Hostname or IP address** (for public IP): the hostname or IP address of the data source.

- **Private Link Connection** (for Private Link): the private link connection that you created in the [Private Link Connections](/tidb-cloud/serverless-private-link-connection.md) section.

hfxsd · 2026-01-19T14:23:10Z

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md

+   - **Hostname or IP address** (for public IP): the hostname or IP address of the data source.
+   - **Private Link Connection** (for Private Link): the private link connection that you created in the [Private Link Connections](/tidb-cloud/serverless-private-link-connection.md) section.
+
+   </CustomContent>


Suggested change

</CustomContent>

</CustomContent>

hfxsd · 2026-01-19T14:23:31Z

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md

   - **Port**: the port of the data source.
   - **Username**: the username of the data source.
   - **Password**: the password of the username.
   - **SSL/TLS**: if you enable SSL/TLS, you need to upload the certificates of the data source, including any of the following:


Suggested change

- **Port**: the port of the data source.

- **Username**: the username of the data source.

- **Password**: the password of the username.

- **SSL/TLS**: if you enable SSL/TLS, you need to upload the certificates of the data source, including any of the following:

- **Port**: the port of the data source.

- **Username**: the username of the data source.

- **Password**: the password of the username.

- **SSL/TLS**: if you enable SSL/TLS, you need to upload the certificates of the data source, including any of the following:

ti-chi-bot bot added first-time-contributor Indicates that the PR was contributed by an external member and is a first-time contributor. missing-translation-status This PR does not have translation status info. labels Sep 30, 2025

ti-chi-bot bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Sep 30, 2025

Add essential migration

8a0992f

xuanyu66 force-pushed the essential-migration branch from 0f27069 to 8a0992f Compare September 30, 2025 02:43

xuanyu66 added area/tidb-cloud This PR relates to the area of TiDB Cloud. for-cloud-release This PR is related to TiDB Cloud release. labels Sep 30, 2025

xuanyu66 changed the title ~~Add essential migration~~ Add essential migration doc Sep 30, 2025

gemini-code-assist bot reviewed Sep 30, 2025

View reviewed changes

xuanyu66 and others added 2 commits September 30, 2025 10:47

Apply suggestions from code review

06a3a33

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

polish

a8035ba

xuanyu66 force-pushed the essential-migration branch from e84c9bc to a8035ba Compare January 12, 2026 06:50

xuanyu66 added 2 commits January 12, 2026 15:00

Merge branch 'release-8.5' into essential-migration

56614c2

private link connection

ba4755a

xuanyu66 requested a review from Copilot January 12, 2026 07:08

Copilot started reviewing on behalf of xuanyu66 January 12, 2026 07:09 View session

Copilot AI reviewed Jan 12, 2026

View reviewed changes

format

31e6e40

xuanyu66 added the translation/no-need No need to translate this PR. label Jan 12, 2026

ti-chi-bot bot removed the missing-translation-status This PR does not have translation status info. label Jan 12, 2026

hfxsd self-assigned this Jan 12, 2026

hfxsd requested a review from zhangyangyu January 12, 2026 10:42

hfxsd changed the title ~~Add essential migration doc~~ cloud: add migration docs for TiDB Cloud Essential Jan 13, 2026

hfxsd requested a review from alastori January 13, 2026 12:15

hfxsd removed the for-cloud-release This PR is related to TiDB Cloud release. label Jan 13, 2026

replace name with {{{ .essential }}}

3bb60ea

hfxsd reviewed Jan 13, 2026

View reviewed changes

tidb-cloud/migrate-from-mysql-using-data-migration-essential.md Outdated Show resolved Hide resolved

hfxsd reviewed Jan 13, 2026

View reviewed changes

tidb-cloud/migrate-from-mysql-using-data-migration-essential.md Outdated Show resolved Hide resolved

zhangyangyu reviewed Jan 19, 2026

View reviewed changes

tidb-cloud/migrate-from-mysql-using-data-migration-essential.md Outdated Show resolved Hide resolved

github-actions bot pushed a commit to qiancai/pingcap-docsite-preview that referenced this pull request Jan 19, 2026

Preview PR pingcap/docs#21849 and this preview is triggered from commit

5d83e18

pingcap/docs@7aeb8ff

zhangyangyu reviewed Jan 19, 2026

View reviewed changes

tidb-cloud/migrate-from-mysql-using-data-migration-essential.md Outdated Show resolved Hide resolved

zhangyangyu reviewed Jan 19, 2026

View reviewed changes

tidb-cloud/migrate-from-mysql-using-data-migration-essential.md Outdated Show resolved Hide resolved

zhangyangyu reviewed Jan 19, 2026

View reviewed changes

tidb-cloud/migrate-from-mysql-using-data-migration-essential.md Outdated Show resolved Hide resolved

zhangyangyu reviewed Jan 19, 2026

View reviewed changes

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration-essential.md Outdated Show resolved Hide resolved

Update tidb-cloud/migrate-from-mysql-using-data-migration.md

0f004c1

Co-authored-by: Grace Cai <[email protected]>

qiancai reviewed Jan 19, 2026

View reviewed changes

tidb-cloud/migrate-from-mysql-using-data-migration.md Show resolved Hide resolved

qiancai reviewed Jan 19, 2026

View reviewed changes

tidb-cloud/migrate-from-mysql-using-data-migration.md Outdated Show resolved Hide resolved

qiancai reviewed Jan 19, 2026

View reviewed changes

tidb-cloud/migrate-from-mysql-using-data-migration.md Outdated Show resolved Hide resolved

polish

a6c3a57

qiancai reviewed Jan 19, 2026

View reviewed changes

tidb-cloud/migrate-from-mysql-using-data-migration.md Outdated Show resolved Hide resolved

use Full + Incremental

db53bf2

qiancai reviewed Jan 19, 2026

View reviewed changes

tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md Outdated Show resolved Hide resolved

qiancai reviewed Jan 19, 2026

View reviewed changes

tidb-cloud/migrate-from-mysql-using-data-migration.md Show resolved Hide resolved

xuanyu66 and others added 3 commits January 19, 2026 17:28

use **Data Migration**

2cd5ffc

Apply suggestions from code review

fe5c2c8

Co-authored-by: Grace Cai <[email protected]>

Update tidb-cloud/migrate-from-mysql-using-data-migration.md

832b566

Co-authored-by: Grace Cai <[email protected]>

qiancai reviewed Jan 19, 2026

View reviewed changes

qiancai and others added 2 commits January 19, 2026 17:49

minor wording fix

49f4e62

fix lint

77fca5e

qiancai reviewed Jan 19, 2026

View reviewed changes

hfxsd reviewed Jan 19, 2026

View reviewed changes

		- During incremental data migration, if the table to be migrated already exists in the target database with duplicate keys, an error is reported and the migration is interrupted. In this situation, you need to verify that the MySQL source data is accurate. If it is, click the Restart button of the migration job, and the migration job will replace the conflicting records in the target cluster with the MySQL source records.

		- During incremental replication (migrating ongoing changes to your cluster), if the migration job recovers from an abrupt error, it might open the safe mode for 60 seconds. During the safe mode, `INSERT` statements are migrated as `REPLACE`, `UPDATE` statements as `DELETE` and `REPLACE`, and then these transactions are migrated to the target TiDB Cloud cluster to ensure that all the data during the abrupt error has been migrated smoothly to the target TiDB Cloud cluster. In this scenario, for MySQL source tables without primary keys or non-null unique indexes, some data might be duplicated in the target TiDB Cloud cluster because the data might be inserted repeatedly into the target TiDB Cloud cluster.

	- If Public IP is selected, fill in the Hostname or IP address field with the hostname or IP address of the data source.
	- If Public is selected, fill in the Hostname or IP address field with the hostname or IP address of the data source.

	- Currently, the Data Migration features is not available for {{{ .starter }}}.
	- Currently, the Data Migration feature is not available for {{{ .starter }}}.


		4. After applying the changes (and restarting if needed), connect to the instance and run the `SHOW VARIABLES` statement in this section to verify the configuration.

		For detailed instructions, see [Set instance parameters](https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-mysql/modify-the-parameters-of-an-apsaradb-rds-for-mysql-instance)

	For detailed instructions, see [Set instance parameters](https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-mysql/modify-the-parameters-of-an-apsaradb-rds-for-mysql-instance)
	For more information, see [Set instance parameters](https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-mysql/modify-the-parameters-of-an-apsaradb-rds-for-mysql-instance).

	> - Can access to your cloud provider's console during the setup process.
	> - Can access your cloud provider's console during the setup process.


		## Step 5: Precheck

		On the Precheck page, you can view the precheck results. If the precheck fails, you need to operate according to Failed or Warning details, and then click Check again to recheck.

		- Data source: the data source type.
		- Region: the region of the data source, which is required for cloud databases only.

		- Connectivity method: the connection method for the data source. <CustomContent plan="dedicated">Currently, you can choose public IP, VPC Peering, or Private Link according to your connection method.</CustomContent><CustomContent plan="essential">You can choose public IP or Private Link according to your connection method.</CustomContent>

		<CustomContent plan="dedicated">

		- Hostname or IP address (for public IP and VPC Peering): the hostname or IP address of the data source.
		- Service Name (for Private Link): the endpoint service name.

		- Hostname or IP address (for public IP): the hostname or IP address of the data source.
		- Private Link Connection (for Private Link): the private link connection that you created in the [Private Link Connections](/tidb-cloud/serverless-private-link-connection.md) section.

cloud: add migration docs for TiDB Cloud Essential #21849

Are you sure you want to change the base?

cloud: add migration docs for TiDB Cloud Essential #21849

Conversation

xuanyu66 commented Sep 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

First-time contributors' checklist

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

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

Do your changes match any of the following descriptions?

Uh oh!

gemini-code-assist bot commented Sep 30, 2025

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

ti-chi-bot bot commented Jan 13, 2026

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

xuanyu66 commented Sep 30, 2025 •

edited

Loading