MySQL

DataArts Migration supports RDS for MySQL on the cloud and the on-premises MySQL data source. It is also compatible with Huawei Cloud DDM and open-source TiDB. It meets data synchronization requirements in different deployment environments.

Preparation and Constraints

Network requirements
The MySQL data source can communicate with CDM. This ensures smooth data transmission. For details, see Enabling Network Connectivity.
Required permissions
- Reading data from an on-premises MySQL database: The account must have the read-only permission (SELECT) on the table to be synchronized so that data can be read securely and accurately.
- Writing data to an on-premises MySQL database: The account must have write permissions (INSERT, DELETE, and UPDATE) on the table to be synchronized so that data can be correctly written to the destination table.
- Table operations (such as creating and deleting a table): The account must have write permissions (CREATE and DROP) on the table to be synchronized so that the table structure can be flexibly adjusted during data integration.
- Note: If the data source is Huawei Cloud DDM, the database selected for the connection must be the same as that in the task because DDM does not support cross-database metadata query. Otherwise, a metadata query error may occur due to database inconsistency.

Driver Selection

Driver Name	How to Obtain	Recommended Version
MySQL	MySQL driver	5.1.48

Supported Data Types

DataArts Migration supports the following field types and their common variants in MySQL 5.7/8.0 Community Edition. This ensures that DataArts Migration can correctly read and write data.

Category	Field Type	MySQL Read	MySQL Write
Integer	TINYINT	√	√
	SMALLINT	√	√
	INTEGER	√	√
	BIGINT	√	√
Floating point number	FLOAT	√	√
	DOUBLE	√	√
	DECIMAL/NUMBERIC	√	√
	REAL	√	√
Character	VARCHAR	√	√
	JSON	√	√
	TEXT	√	√
	MEDIUMTEXT	√	√
	LONGTEXT	√	√
Binary	VARBINARY	√	√
	BINARY	√	√
	TINYBLOB	√	√
	MEDIUMBLOB	√	√
	LONGBLOB	√	√
Enumeration	ENUM	√	√
Enumeration	SET	√	√
Boolean	BOOLEAN	√	√
Bit	BIT	√	√
Time	DATE	√	√
	DATETIME	√	√
	TIMESTAMP	√	√
	TIME	√	√
	YEAR	√	√

Supported Migration Scenarios

DataArts Migration supports the following offline synchronization modes:

Single table synchronization
DataArts Migration supports table/file synchronization in data ingestion into a data lake or data migration to the cloud.
Database and table shard synchronization
DataArts Migration supports synchronization of data from multiple databases and tables in data ingestion into a data lake or data migration to the cloud.
Entire DB migration
DataArts Migrations supports synchronization of data from an on-premises database in data ingestion into a data lake or data migration to the cloud.

DataArts Migration supports synchronization of data from an on-premises database to the cloud. For details about the supported data source types, see the data source types supported by entire database synchronization.

Database and table shard synchronization and entire DB migration are not supported in all regions. The following table lists the supported MySQL migration scenarios.

Supported Migration Scenario	MySQL Single Table Read	MySQL Single Table Write	MySQL Database/Table Shard Read	MySQL Database/Table Shard Write	MySQL Entire DB Read	MySQL Entire DB Write
Supported	√	√	√	√	√	x

Core Capabilities

Connection configuration

Configuration Item	Supported	Description
User/AK	√	User authentication ensures connection security.
SSL encryption	√	SSL encryption ensures secure data transmission. Currently, SSL authentication can be enabled only for RDS.
SSL authentication	√	Currently, SSL authentication can be enabled only for RDS. The standard Huawei Cloud CA certificate is used for authentication.
Private certificate	x	Private certificates are not supported.
Connection configuration optimization	√	Connection configuration such as connectTimeout can be optimized to improve connection performance.
Custom driver	√	Custom drivers are supported and provide better flexibility.

Read capabilities

Configuration Item	Supported	Description
Shard concurrency	√	Horizontal sharding based on primary keys or common fields and multi-thread concurrent extraction significantly improve the throughput and efficiency.
Dirty data processing	√	Abnormal data can be written to the dirty data bucket to prevent job failures caused by a small amount of abnormal data.
Custom fields	√	You can add computed columns, constant columns, or masking functions for tasks to meet personalized service requirements.
Incremental read	√	Where conditions and the SQL mode enable incremental data reading.
Stream and batch reading	Stream read	Data can be read from streams. This is applicable to migration of a large amount of data.
View read	√	Data can be read from views. This enables flexible data integration and processing.

Write capabilities

Configuration Item	Supported	Description
Dirty data processing	√	Abnormal data can be written to the dirty data bucket to prevent job failures caused by a small amount of abnormal data.
Conflict resolution	√	Multiple write modes, such as insert into, replace into, and duplicate key, can flexibly handle data conflicts.
Pre- and post-import processing	√	Operations such as preSql and delete can clean and process data before and after data import.
Concurrent write	√	Concurrent write improves efficiency.
Optimization of the number of written rows	√	You can improve write performance by adjusting the values of parameters Commit Size and Batch Size in the connection configuration.