Skip to content
This repository was archived by the owner on Jan 3, 2025. It is now read-only.

Commit ddb8414

Browse files
Update en/shard-merge-best-practices.md
Co-authored-by: TomShawn <[email protected]>
1 parent 3e5d500 commit ddb8414

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

en/shard-merge-best-practices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,7 @@ Then you can perform the following steps to fix the `ERROR 1062 (23000): Duplica
119119

120120
## Special processing when the upstream RDS contains sharded tables
121121

122-
If the upstream data source is an RDS and it contains sharded tables, the table names in MySQL binlog might be invisible when connecting to the SQL client. For example, if the upstream is a UCloud distributed database, the table name in MySQL binlog might have a prefix `_0001`. Therefore, you need to configure [table routing](dm-key-features.md#table-routing) based on the table names in MySQL binlog, instead of those in the SQL client.
122+
If the upstream data source is an RDS and it contains sharded tables, the table names in MySQL binlog might be invisible when connecting to a SQL client. For example, if the upstream is a UCloud distributed database, the table name in the binlog might have an extra prefix `_0001`. Therefore, you need to configure [table routing](dm-key-features.md#table-routing) based on the table names in binlog, instead of those in the SQL client.
123123

124124
## Create/drop tables in the upstream
125125

0 commit comments

Comments
 (0)