Db2 to Kafka

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

Target DataSource：

Kafka

Connection

Function	Description
Schema Migration	If the specified Topic after mapping does not exist in the Target, BladePipe will automatically create the Topic, allowing setting the number of partitions.
Full Data Migration	Migrate data by sequentially scanning data in tables and writing it in batches to the message-oriented middleware.
Incremental Data Sync	Sync of common DML like INSERT, UPDATE, DELETE is supported.
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 LSN to consume the incremental data logs from a specific LSN.
Metadata Retrieval	Retrieve the target metadata with filtering conditions or target primary keys set from the source table.

Function	Description
Message Format	The following message formats are supported. See Message Format. CloudCanal format AlibabaCanal format
Topic Mapping Rules	By default, Topic is formed by connecting source instance id, database, and table with . in between (e.g., my-vgpq6q097174t6t.dingtax.app_key). Also, it supports the mapping rules, namely, keeping the name the same as that in Source, converting the text to lowercase, converting the text to uppercase.
Table-level Topic	Create Topics corresponding to the tables in the Source, and the table partitions can be obtained automatically.
DDL Dedicated Topic	Allow specifying a Topic for DDL. If not specified, DDL time is placed in partition 0 of the Topic created from the corresponding table.
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.
Data Filtering Conditions	Support data filtering using WHERE conditions, with SQL-92 as the SQL language. For more information, see Data Filtering.

Prerequisite	Description
Preparation for Db2 CDC (Incremental)	See Preparation for Db2 CDC

Parameter	Description
fullBatchSize	Number of records per batch written to the Target in full data migration, significantly affecting migration performance.
fullPagingCount	Page size for scanning data in a source relational database.
scanParallel	Number of threads for parallel data scanning in the source database. If the data source is a relational database, it refers to the number of tables scanned in parallel.
eventStoreSize	Size of the queue in the memory (it might be event count or memory size in bytes).
maxTxsPerIteration	Number of transactions scanned by the Worker.
iterateIntervalMs	Interval between transaction scans (in milliseconds).
snapshotRead	Whether to scan the whole table (select column_name from table) to read the source database.
filterDDL	Whether to synchronize DDL in incremental data synchronization. If the value is true, DDL synchronization is not performed.
metaFreshCoolMs	Waiting time for metadata refresh.
metaFreshCount	Metadata refresh count.
cdcAutoClear	Whether to enable automatic cleanup of CDC tables.
cdcClearIntervalMin	Interval for clean up CDC tables (in minutes).
dbHeartBeatEnable	Enable heartbeat for the source database.

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

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

Parameter	Description
schemaFormat	Message format. For more information, see Message Format.
batchWriteSize	The maximum data size of a single message. If the size exceeds the limit, the message will be split.
defaultTopic	Messages that cannot find a corresponding topic are sent to this topic (such as adding a new table)
ddlTopic	A topic specifically used to receive DDL events. If it is empty, the DDL events will be sent to the 0th partition of the corresponding topic.
compressionType	Kafka compression.type parameter to set compression algorithm. Support GZIP, SNAPPY, LZ4, ZSTD.
batchSize	Kafka batch.size parameter.
acks	Kafka acks parameter. By default, it is all.
maxRequestBytes	Kafka max.request.size parameter.
lingerMs	Kafka linger.ms parameter. By default, it is 1.
envelopSchemaInclude	When schemaFormat is set to DEBEZIUM_ENVELOP_JSON_FOR_MQ, it means whether the message body contains schema information.
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.