Kafka to MySQL

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

Target DataSource：

MySQL

Connection

Function	Description
Incremental Data Sync	Allow subscribing to messages from the source Topic and transforming them into DML operations, namely, INSERT, UPDATE, DELETE.
Subscription Modification	Add, delete, or modify the subscribed topics. For more information, see Modify Subscription.
Position Resetting	Reset positions by timestamp to consume the data in a past period again.

Function	Description
Message Format	The following message formats are supported. See Message Format. CloudCanal format AlibabaCanal format
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.
Incremental Data Write Conflict Resolution Rule	IGNORE: Ignore primary key conflicts (skip writing), REPLACE: Replace the entire row in case of primary key conflicts.
Handling of Zero Value for Time	Allow setting zero value for time to different data types to prevent errors when writing to the Target.

Limit	Description
Creating Tables in the Target in Advance	Only support automatic Topic creation for messages.
Raw Message Format	Only support raw message replication from Kafka to Kafka, and Raw Message Format needs to be selected at both the Source and the Target.

Prerequisite	Description
Port Preparation	Allow the migration and sync node (Worker) to connect to the Kafka ports.

Parameter	Description
schemaFormat	MQ Message format. For more information, see Message Format.
consumerGroupId	Kafka consumer group ID.
consumeParallel	Degree of consuming Kafka topics in parallel.
sessionTimeoutMs	Kafka session timeout in milliseconds.
maxPollRecords	Maximum number of messages fetched in one poll from Kafka.
dbHeartbeatIntervalSec	Interval for initiating heartbeat on the source database.
dbHeartbeatToleranceStep	The threshold of gap between the latest offset and the current offset. If the actual gap is bigger than the threshold, BladePipe won‘t send heartbeat message.
customClientProps	Custom properties passed to the Kafka client in JSON format. The key is the parameter name and the value is the parameter value. This setting takes the highest priority. For example: AWS IAM Access Control

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

Prerequisite	Description
Permissions for Account	See Permissions Required for MySQL/MariaDB.
Port Preparation	Allow the migration and sync node (Worker) to connect to the MySQL/MariaDB port (e.g., 3306).

Parameter	Description
keyConflictStrategy	Strategy for handling primary key conflicts during write in Incremental DataTask: IGNORE: Ignore conflicts (default) REPLACE: Replace conflicts (optional)
dstWholeReplace	Convert INSERT and UPDATE operations into full row replacement in the Target.
deCycle	Enable filtering in bidirectional sync to filter DML/DDL with specific markers.
specialSqlMode	Set a specific SQL mode when initializing the connection between databases.
defaultGisSRID	Set the SRID for GIS data types.
dstTimeZone	Target time zone, e.g., +08:00, Asia/Shanghai, America/New_York, etc.
increParallelApplyStrategy	Parallel write strategy for relational databases in the Target: KEY: Parallel writing to partitions separated based on primary keys. TABLE: Parallel writing to partitions separated based on tables. KEY_UPGRADE_TABLE: Parallel writing to partitions separated based on primary keys. Upgrade the partition to a table if there is an update to the unique key.

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