TiCDC 4.0.13 Synchronization to MySQL 8.0.34

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

Original topic: ticdc4.0.13同步到mysql8.0.34

| username: 路在何chu

[TiDB Usage Environment] Production Environment
[TiDB Version]
[Reproduction Path] What operations were performed when the problem occurred
TiDB synchronized to 8.0.13 through TiCDC
[Encountered Problem: Problem Phenomenon and Impact]
I would like to consult with everyone, has anyone done this before? What should be noted? According to my understanding, this should be possible, but I haven’t done it specifically yet.

| username: Kongdom | Original post link

:yum: Only supports transmission with the same database name

| username: 像风一样的男子 | Original post link

Support is definitely available.

However, if the data volume of the host group is large, MySQL may not be able to handle it.

| username: 路在何chu | Original post link

Yes, it definitely needs to have the same database name.

| username: 路在何chu | Original post link

Well, I upgraded it, and it doesn’t seem to have any errors. It should be fine.

| username: 随缘天空 | Original post link

In theory, there should be no problem, but it is best to confirm some special DDL statements, functions, and stored procedures after migration.

| username: Kongdom | Original post link

:joy: Are we the only ones transferring between databases with different names?