Configure TiCDC to synchronize the t1 table in the db1 database of TiDB to the t1 table in the db2 database of TiDB

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

Original topic: ticdc配置tidb的db1库t1表同步到tidb的db2t1表

| username: sunshaoqing

How to configure filtering and routing to synchronize the t1 table from the db1 database in TiDB to the t1 table in the db2 database in TiDB using ticdc, only synchronizing one table? Seeking expert advice.

| username: hey-hoho | Original post link

As of the latest version, according to the documentation, TiCDC still does not support schema routing, meaning that database and table names cannot be changed.

However, filter rules can be set. Refer to:

| username: sunshaoqing | Original post link

Yes, I checked many places and none of them mentioned routing.

| username: tidb菜鸟一只 | Original post link

Are they two separate clusters?

| username: sunshaoqing | Original post link

Does the drainer have routing functionality in the same cluster?

| username: dba-kit | Original post link

What is the application scenario? Do we still need to use TiCDC in the same cluster? Can views satisfy the requirement?

| username: tidb菜鸟一只 | Original post link

Isn’t it possible to query directly within the same cluster?

| username: sunshaoqing | Original post link

The performance of the partitioned table is too poor and needs to be converted to a regular table. I really can’t think of any way to do it.

The current idea is to use Dumpling to export the data, edit the table structure, import it into TiDB, and then use a synchronization tool to incrementally sync the partitioned table data to the regular table. Finally, rename the table.

| username: tidb菜鸟一只 | Original post link

What aspects of partitioned table performance are poor? Can it only be optimized by rebuilding the table?

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.