BladePipe 1.7.0: Stronger alerts, Broader DB support, Faster KingbaseES scanning.
Skip to main content

Aurora for MySQL to Doris

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

Target DataSource:

Connection

Basic Functions

FunctionDescription
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.

Data Verification and Correction

Verify all existing data. Optionally, you can correct the inconsistent data based on verification results. Scheduled DataTasks are supported.
For more information, see Create Verification and Correction DataJob.

Subscription Modification

Add, delete, or modify the subscribed tables with support for historical data migration. For more information, see Modify Subscription.

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, MODIFY COLUMN, RENAME COLUMN, DROP COLUMN
  • RENAME TABLE
  • CREATE TABLE (whole database sync).
Metadata Retrieval

Retrieve the target metadata with filtering conditions or target primary keys set from the source table.

Advanced Functions

FunctionDescription
Removal of Target Data before Full Data Migration

Remove the existing data in the Target before running the Full Data Migration, applicable for DataJobs reruning and scheduled Full Data migrations.

Recreating Target Table

Recreate target tables before running the Full Data Migration, applicable for DataJobs reruning and scheduled Full Data migrations.

Stream Load

Use Stream Load to write data to Doris/SelectDB BE. By default, batch write is adopted, with dynamic adjustment of data flush interval and batch size.

Handling of Zero Value for Time

Allow setting zero value for time to different data types to prevent errors when writing to the Target.

Online DDL Compatibility

Supports synchronization for GH-OST, PT-OSC, Aliyun DMS Online DDL, and PT_GHOST.

Setting Data Partitions

When creating a DataJob, specify partition definitions at the table level (static or dynamic). Automatically add these partition definitions during schema migration.

Scheduled Full Data Migration

For more information, see Create Scheduled Full Data DataJob.

Custom Code

For more information, see Custom Code Processing, Debug Custom Code and Logging in Custom Code.

Adding Virtual Columns

Support adding custom virtual columns with fixed values, such as region, ID, etc.

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

LimitDescription
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.

Target Table Type

Only support Unique key model(Unique).

Source Table Type

Migration and sync of tables without primary keys are not supported.

Data Type

Do not support binary data such as BINARY, BLOB.

Incremental Data Write Conflict Resolution Rule

Using Stream Load method, the primary key is used for full row replacement.


Source

Prerequisites

PrerequisiteDescription
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

ParameterDescription
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

PrerequisiteDescription
Permissions for Account

SELECT and DDL permissions (optional)

Port Preparation

Allow the migration and sync node (Worker) to connect to the Doris/SelectDB FE QueryPort and FE/BE HttpPort.

Parameters

ParameterDescription
host

MySQL port, corresponding to Doris/SelectDB FE QueryPort.

httpHost

Host for Doris stream load, corresponding to Doris/SelectDB FE/BE HttpPort.

totalDataInMemMb

Maximum data size allowed in memory when writing in batches; If the data size exceeds the memory limit, or the wait time exceeds asyncFlushIntervalSec, then data is flushed to the write queue.

asyncFlushIntervalSec

Interval to wait for flushing when writing in batches; If the wait time exceeds asyncFlushIntervalSec, or the data size exceeds totalDataInMemMb, then data is flushed to the write queue.

flushBatchMb

Maximum batch size per table; If the batch size exceeds this limit, then data is flushed to the write queue.

realFlushPauseSec

Wait time to flush data to Doris/SelectDB using stream load. 0 means no wait is needed.

soTimeoutSec

TCP socket timeout (so_timeout) during QueryPort operations.

enableTimeZoneProcess

Enable time zone conversion for time fields.

timezone

Timezone in the Target, e.g., +08:00 Asia/Shanghai America/New_York.

maxInSizePerQuery

Maximum number of IN clause values per query during secondary verification. Queries exceeding this limit will be automatically split.

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