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

MySQL to Paimon

BladePipe supports data replication from MySQL to Paimon. 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.
UPDATE and DELETE for tables without primary keys are not synced by default (manual selection required).

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, DROP COLUMN, MODIFY COLUMN, CHANGE COLUMN

Metadata Retrieval

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

Advanced Functions

FunctionDescription
Write Conflict Resolution Rule

For the source tables with primary keys, data is overwritten to the Target. For the source tables without primary keys, data is appended to the Target.

Custom Table Properties

Configure format-version and other table properties.

Setting Data Partitions

When creating a DataJob, specify partition definitions at the table level (separated by comma). Automatically add these partition definitions during schema migration.

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

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.


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
Port Preparation

Allow the migration and sync node (Worker) to connect to the Catalog and Warehouse.

S3 Catalog Configuration Template
  • CatalogUri: glue.ap-southeast-1.amazonaws.com

  • httpsEnabled: true

  • metastoreType: filesystem

  • warehouse : s3://warehouse/test

  • catalogProps: { "s3.access-key": "", "s3.secret-key": "", "s3.path-style-access": "true" }

Parameters

ParameterDescription
writeParallel

The number of parallel threads allowed to write data to the Target, significantly affecting migration or synchronization performance.

writeProps

Write configuration (Json format)

compactTaskSize

Compression task thread count

paimonIOManagerPaths

I/O manager path

defaultDynamicBucket

Default dynamic Bucket count

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 Paimon. 0 means no wait is needed.

catalogUri

Catalog URI

httpsEnabled

Enable HTTPS for Catalog URI

catalogWarehouse

Specify the root directory URI of the Paimon warehouse

catalogMetastoreType

Enable file system mode

catalogProps

Catalog configuration

enableTimeZoneProcess

Whether to convert time zone on time fields

timezone

Target time zone, e.g., +08:00, Asia/Shanghai, America/New_York, etc.

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