Aurora for MySQL 到 AutoMQ

选择对端数据库：

AutoMQ

数据链路

基本功能

功能	说明
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 file position or timestamp. Allow re-consumption of incremental data logs in a past period or since a specific Binlog file and position.
Metadata Retrieval	Retrieve the target metadata with filtering conditions or target primary keys set from the source table.

高级功能

功能	说明
消息格式	支持以下消息格式，文档：消息格式说明 CloudCanal内置格式 AlibabaCanal兼容格式
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.
Setting Target Primary Key	Change the primary key to another field.

限制和注意点

限制项	说明
MySQL 存储引擎	支持 InnoDB, MySIAM, 阿里云 XEngine, 其他存储引擎暂未测试
MySQL 字符集	支持 utf8, utf8mb4, latin1, 其他编码暂未测试

使用示例

标题	详情
CloudCanal x AutoMQ 数据迁移同步	文档：CloudCanal x AutoMQ 数据迁移同步
跨互联网数据互通 (AutoMQ)	文档：跨互联网数据互通 (AutoMQ)
AutoMQ 数据中转校验	文档：AutoMQ 数据中转校验
MySQL to Kafka / AutoMQ Data Migration Sync	Documentation: MySQL to Kafka / AutoMQ Data Migration Sync

链路FAQ

• MySQL 任务延迟怎么办?

• MySQL 源端找不到 binlog 文件

• 如何打开 MySQL 源端心跳?

• MySQL 源端 Schema 权限报错怎么办?

  Tips: MySQL 源端相关 FAQ 同样适用于 MySQL 系数据源。

---

源端数据源

前置条件

条件	说明
账号权限	文档：MySQL / MariaDB 需要的权限
开启 Binlog	[mysqld] log-bin=mysql-bin # 开启 Binlog binlog-format=ROW # 选择 ROW 模式 binlog_row_image=FULL # 变更带所有列数据

任务参数

参数名称	说明
parseBinlogParallel	增量解析 Binlog 的并发数
parseBinlogBufferSize	用于增量解析 Binlog 的环形队列大小
maxTransactionSize	单事务最大数据条数，超过则分段刷出
limitThroughputMb	限制增量 Binlog 流量
extraDDL	兼容额外的 DDL 同步，包括 PT, GHOST, ALI_DMS, PT_GHOST
fullDataSqlConditionEnabled	将过滤条件拼入 SQL 中进行源端数据扫描，此参数只针对全量迁移有效
srcTimeZone	源端时区，例如 +08:00, Asia/Shanghai, America/New_York 等

Tips: 通用参数配置请参考 通用参数及功能

---

目标端数据源

前置条件

条件	说明
网络准备	迁移同步节点（sidecar）可连接 AutoMQ 各节点

任务参数

参数名称	说明
schemaFormat	消息格式，文档：消息格式说明
batchWriteSize	单条消息最大数据条数，超过则拆分消息
defaultTopic	无法找到对应 Topic 的消息则发送到此 Topic (如新增表)
ddlTopic	专门发送 DDL 的 Topic, 为空则发送到对应 Topic 的第 0 个分区
compressionType	AutoMQ compression.type 参数, 设置压缩算法, 支持 GZIP, SNAPPY, LZ4, ZSTD 算法
batchSize	AutoMQ batch.size 参数
acks	AutoMQ acks 参数, 默认 all
maxRequestBytes	AutoMQ max.request.size 参数
lingerMs	AutoMQ linger.ms 参数, 默认 1
envelopSchemaInclude	当 schemaFormat 设置为 DEBEZIUM_ENVELOP_JSON_FOR_MQ 时，消息体是否包含 schema 信息

Tips: 通用参数配置请参考 通用参数及功能