Selection between TiDB Data Migration and Otter

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: TiDB Data Migration与otter的选型

| username: 我是吉米哥

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
I want to aggregate and synchronize multiple upstream MySQL clusters to a TiDB cluster for report querying. Which solution is better?
Need to synchronize DDL, but I see that DM has some DDL limitations.
Is TiDB Data Migration less compatible with MySQL compared to Otter?
Can anyone with experience share their insights? Thanks.

| username: 这里介绍不了我 | Original post link

Personally, I feel that whether using DM or Otter, if the downstream is TiDB, the issue of DDL compatibility will always exist.

| username: wakaka | Original post link

Did you use unsupported DDL with DM?

| username: wakaka | Original post link

There is documentation on handling failed DDL statements at 使用 TiDB Data Migration 处理出错的 DDL 语句 | PingCAP 文档中心. You can test it more.

| username: 有猫万事足 | Original post link

You dare to use this otter, I can only respect you as a brave man.

Fixes are also calculated on a monthly basis.
If my boss isn’t pointing a gun at me, I wouldn’t spend much time researching it. The documentation and communication both feel very difficult.