DM (Data Migration) 是一体化数据同步任务管理平台

• Remove the restriction of "the next shard DDL statement cannot be executed unless the current shard DDL operation is completely finished in shard merge scene for binlog replication" #177
• Support retry task on the invalid connection error for binlog replication #66
• Support generating -schema-create.sql files automatically for full migration #186
• Use TiDB SQL Parser to parse and restore DDL statements in binlog query events, and remove the use db statement when replicating to downstream #54
• Support migrating tables with generated column for full migration and binlog replication #42 #60
• Support appending the task name as a suffix to the dumped data directory (dir in the task configuration file) for full migration #100
• Support resuming tasks automatically after the DM-worker process restarted #88 #116
• Support skipping pre-check items when starting tasks #65
• Support case-insensitive in binlog event type of Binlog Event Filter rules #188
• Optimize relay log mechanism to improve compatibility with upstream MySQL/MariaDB #92 #108 #117 #140 #171
• Optimize RPC framework to limit the concurrency between DM-master and DM-worker #157
• Redirect the log of mydumper into the log of DM-worker #93
• Support using --print-sample-config command flag to show the sample config of DM-worker and DM-master #28
• Support showing the status of sharding DDL replication in the Grafana dashboard and optimize the dashboard #96 #101 #120
• Support setting the max_allowed_packet parameter for the database connection to the upstream and downstream #99
• Support using unsafe_cleanup in DM Ansible to clean components of DM cluster #128
• Fix flushing checkpoint wrongly when existing multiple sharding groups #124
• Fix the wrong progress status when loading dumped files #89
• Greatly improve the test to ensure correctness
• Fix many other bugs that don't affect correctness

New Features

• Support the full data migration and the incremental data migration from MySQL/MariaDB into TiDB
• Support running multi independent synchronization tasks concurrently on one DM-worker instance
• Support synchronizing a certain table of the upstream MySQL/MariaDB instance to the specified table in TiDB by table routing
• Support only synchronizing or filtering all operations of some databases or some tables by black and white lists
• Support synchronizing or filtering some of the binlog events by binlog event filter
• Support modifying auto-increment primary key fields to resolve the conflicts for shard tables by column mapping
• Support merging the original shard instances and tables into TiDB but with some restrictions
• Support synchronizing data definition changed by online DDL tools (including pt-osc and gh-ost)
• Support handling synchronization trouble caused by DDL which is not supported by TiDB