Aurora for MySQL to Tunnel

BladePipe supports data replication from Aurora for MySQL to Tunnel. View supported migration, sync, verification, and connector capabilities.

Target DataSource：

Tunnel

Connection

Basic Functions

Function	Description
Schema Migration	If the target schema does not exist, BladePipe will automatically generate and execute CREATE statements based on the source metadata and the mapping rule.
Full Data Migration	Migrate data by sequentially scanning data in tables and writing it in batches to the target database.
Incremental Data Sync	Sync of common DML like INSERT, UPDATE, DELETE is supported. UPDATE and DELETE for tables without primary keys are not synced by default (manual selection required).
Position Resetting	Reset positions by file position or timestamp. Allow re-consumption of incremental data logs in a past period or since a specific Binlog file and position.
Table Name Mapping	Support the mapping rules, namely, keeping the name the same as that in Source, converting the text to lowercase, converting the text to uppercase, truncating the name by "_digit" suffix.
DDL Sync	ALTER TABLE ADD COLUMN, DROP COLUMN, MODIFY COLUMN, CHANGE COLUMN ADD INDEX RENAME TABLE CREATE TABLE (whole database sync) Table partitioning Other compatible DDL
Metadata Retrieval	Retrieve the target metadata with filtering conditions or target primary keys set from the source table.

Advanced Functions

Function	Description
Custom Code	For more information, see Custom Code Processing, Debug Custom Code and Logging in Custom Code.
Setting Target Primary Key	Change the primary key to another field to facilitate data aggregation and other operations.
Data Filtering Conditions	Support data filtering using WHERE conditions, with SQL-92 as the SQL language. For more information, see Data Filtering.

Limits

Limit	Description
MySQL Storage Engine	Support InnoDB, MyISAM, AWS XEngine. Other storage engines have not been tested yet.
MySQL Character Set	Support utf8, utf8mb4, latin1. Other encodings have not been tested yet.

Examples

Title	Details
Cross-Internet Data Synchronization	See Cross-Internet Data Synchronization

FAQ

• How to handle MySQL DataJob latency?

• What to do when binary Log cannot be found in MySQL Source?

• What to do when access to schema in MySQL Source is denied?

  Tip: MySQL source-related FAQ also applies to MySQL-based DataSources.

---

Source

Prerequisites

Prerequisite	Description
Permissions for Account	See Permissions Required for MySQL/MariaDB.
Enabling Binlog	[mysqld] log-bin=mysql-bin # Enable Binlog binlog-format=ROW # Choose ROW mode binlog_row_image=FULL # Changes include all column data

Parameters

Parameter	Description
parseBinlogParallel	Number of threads for parallel parsing of Binlog in Incremental DataJobs.
parseBinlogBufferSize	Size of the circular buffer for parsing Binlog in Incremental DataJobs.
maxTransactionSize	Maximum number of data rows per transaction. If exceeded, the transaction will be split and flushed in parts.
limitThroughputMb	Limit the throughput of incremental Binlogs.
extraDDL	Support synchronization of additional DDL, including PT, GHOST, ALI_DMS, and PT_GHOST.
needJsonEscape	Escape special characters in JSON to be written to the target database.
fullDataSqlConditionEnabled	Add filtering conditions in SQL during source data scanning. It only works in Full Data migration.
srcTimeZone	Source time zone, e.g., +08:00, Asia/Shanghai, America/New_York, etc.

Tips: To modify the general parameters, see General Parameters and Functions.

---

Target

Prerequisites

Prerequisite	Description
Port Preparation	For BladePipe (Docker version), modify the docker-compose.yml port mappings before installing/upgrading after extraction, and open relevant ECS security group ports for remote connection.

Parameters

Parameter	Description
writeParallel	Concurrency level for writing on the other end, significantly impacts migration or synchronization performance.
batchWriteSize	The maximum data size of a single message.
deCycle	Prevent circular data replication.
deCycleFlag	Default marker to prevent circular data replication.
protocol	Protocol for data transfer in Tunnel. Support HTTP currently.
uriPrefix	URI prefix for Tunnel data sources.
contentCompressType	Data compression form for Tunnel data sources. Support DeInflater / GZIP currently.
dbs	Definition of the data source schema.
printDataInLog	Enable to print key data to logs for troubleshooting. Enabling this feature may impact performance and data security.
schemaFormat	Type of Value Schema.
printCustomCodeDebugLog	Print custom code DEBUG logs (Note that it will print data before and after processing, which may increase disk usage and impact sync performance). This parameter takes effect dynamically and DataJob restart is not required.

Tips: To modify the general parameters, see General Parameters and Functions.