Skip to content

v8.5.6: DM supports MySQL 8.4 (#22505) #22676

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ti-chi-bot wants to merge 4 commits into
base: feature/preview-v8.5.6
Choose a base branch
from
+47 −7
Open

v8.5.6: DM supports MySQL 8.4 (#22505) #22676

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6d273a5
cloud: add private link firewall rules for clusters on AWS and Alibab…
hfxsd Apr 1, 2026
896c0c1
DM: MySQL 8.4 support is now available
dveeden Feb 26, 2026
6dc85cf
fix format
Oreoxmt Mar 17, 2026
9db8e52
Rest LGTM
qiancai Mar 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions dm/dm-compatibility-catalog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,9 +19,9 @@ DM supports migrating data from different sources to TiDB clusters. Based on the
| MySQL ≤ 5.5 | Not tested | |
| MySQL 5.6 | GA | |
| MySQL 5.7 | GA | |
| MySQL 8.0 | GA | Does not support binlog transaction compression [Transaction_payload_event](https://dev.mysql.com/doc/refman/8.0/en/binary-log-transaction-compression.html). |
| MySQL 8.1 ~ 8.3 | Not tested | |
| MySQL 8.4 | Incompatible | For more information, see [DM Issue #11020](https://github.com/pingcap/tiflow/issues/11020). |
| MySQL 8.0 | GA | Does not support [binlog transaction compression (`Transaction_payload_event`)](https://dev.mysql.com/doc/refman/8.0/en/binary-log-transaction-compression.html). |
| MySQL 8.1 ~ 8.3 | Not tested | Does not support [binlog transaction compression (`Transaction_payload_event`)](https://dev.mysql.com/doc/refman/8.0/en/binary-log-transaction-compression.html). |
| MySQL 8.4 | Experimental (supported starting from TiDB v8.5.6) | Does not support [binlog transaction compression (`Transaction_payload_event`)](https://dev.mysql.com/doc/refman/8.4/en/binary-log-transaction-compression.html). |
| MySQL 9.x | Not tested | |
| MariaDB < 10.1.2 | Incompatible | Incompatible with binlog of the time type. |
| MariaDB 10.1.2 ~ 10.5.10 | Experimental | |
Expand Down
24 changes: 22 additions & 2 deletions tidb-cloud/set-up-private-endpoint-connections-on-alibaba-cloud.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,8 @@ To connect to your {{{ .starter }}} or {{{ .essential }}} cluster via a private

1. [Choose a TiDB cluster](#step-1-choose-a-tidb-cluster)
2. [Create a private endpoint on Alibaba Cloud](#step-2-create-a-private-endpoint-on-alibaba-cloud)
3. [Connect to your TiDB cluster using the private endpoint](#step-3-connect-to-your-tidb-cluster-using-the-private-endpoint)
3. [Authorize your private endpoint in TiDB Cloud](#step-3-authorize-your-private-endpoint-in-tidb-cloud)
4. [Connect to your TiDB cluster using the private endpoint](#step-4-connect-to-your-tidb-cluster-using-the-private-endpoint)

### Step 1. Choose a TiDB cluster

Expand Down Expand Up @@ -50,7 +51,26 @@ To use the Alibaba Cloud Management Console to create a VPC interface endpoint,
8. Click **OK** to create the endpoint.
9. Wait for the endpoint status to become **Active** and the connection status to become **Connected**.

### Step 3: Connect to your TiDB cluster using the private endpoint
### Step 3. Authorize your private endpoint in TiDB Cloud

After creating the interface endpoint on Alibaba Cloud, you must add it to your cluster's allowlist.

1. On the [**Clusters**](https://tidbcloud.com/project/clusters) page, click the name of your target {{{ .starter }}} or {{{ .essential }}} cluster to go to its overview page.
2. Click **Settings** > **Networking** in the left navigation pane.
3. Scroll down to the **Private Endpoint** section and then locate the **Authorized Networks** table.
4. Click **Add Rule** to add a firewall rule.

- **Endpoint Service Name**: paste the service name you got from [Step 1](#step-1-choose-a-tidb-cluster).
- **Firewall Rule Name**: enter a name to identify this connection.
- **Your Endpoint ID**: paste your 23-character endpoint ID from the Alibaba Cloud Management Console (starts with `ep-`).

> **Tip:**
>
> To allow all Private Endpoint connections from your cloud region (for testing or open access), enter a single asterisk (`*`) in the **Your Endpoint ID** field.

5. Click **Submit**.

### Step 4. Connect to your TiDB cluster using the private endpoint

After you have created the interface endpoint, go back to the TiDB Cloud console and take the following steps:

Expand Down
24 changes: 22 additions & 2 deletions tidb-cloud/set-up-private-endpoint-connections-serverless.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,8 @@ To connect to your {{{ .starter }}} or {{{ .essential }}} cluster via a private

1. [Choose a TiDB cluster](#step-1-choose-a-tidb-cluster)
2. [Create an AWS interface endpoint](#step-2-create-an-aws-interface-endpoint)
3. [Connect to your TiDB cluster](#step-3-connect-to-your-tidb-cluster)
3. [Authorize your private endpoint in TiDB Cloud](#step-3-authorize-your-private-endpoint-in-tidb-cloud)
4. [Connect to your TiDB cluster](#step-4-connect-to-your-tidb-cluster)

### Step 1. Choose a TiDB cluster

Expand Down Expand Up @@ -102,7 +103,26 @@ aws ec2 create-vpc-endpoint --vpc-id ${your_vpc_id} --region ${region_id} --serv

Then you can connect to the endpoint service with the private DNS name.

### Step 3: Connect to your TiDB cluster
### Step 3. Authorize your private endpoint in TiDB Cloud

After creating the AWS interface endpoint, you must add it to your cluster's allowlist.

1. On the [**Clusters**](https://tidbcloud.com/project/clusters) page, click the name of your target {{{ .starter }}} or {{{ .essential }}} cluster to go to its overview page.
2. Click **Settings** > **Networking** in the left navigation pane.
3. Scroll down to the **Private Endpoint** section and then locate the **Authorized Networks** table.
4. Click **Add Rule** to add a firewall rule.

- **Endpoint Service Name**: paste the service name you got from [Step 1](#step-1-choose-a-tidb-cluster).
- **Firewall Rule Name**: enter a name to identify this connection.
- **Your VPC Endpoint ID**: paste your 22-character VPC Endpoint ID from the AWS Management Console (starts with `vpce-`).

> **Tip:**
>
> To allow all Private Endpoint connections from your cloud region (for testing or open access), enter a single asterisk (`*`) in the **Your VPC Endpoint ID** field.

5. Click **Submit**.

### Step 4. Connect to your TiDB cluster

After you have created the interface endpoint, go back to the TiDB Cloud console and take the following steps:

Expand Down
Loading