MySQL to Kudu

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

Target DataSource：

Kudu

Connection

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.
Data Verification and Correction	Verify all existing data. Optionally, you can correct the inconsistent data based on verification results. Scheduled DataTasks are supported.
Subscription Modification	Add, delete, or modify the subscribed tables with support for historical data migration. For more information, see Modify Subscription.
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.
Metadata Retrieval	Retrieve the target metadata with filtering conditions or target primary keys set from the source table.

Function	Description
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.

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.

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

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.

Prerequisite	Description
Network Preparation	The sidecar node must be able to connect to Kudu Masters and Tablet Server nodes.

Parameter	Description
writeParallel	Number of parallel writes to the target.
batchSize	Maximum number of records per single write.
retryCount	Number of retries on write errors.

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