You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In downstream database, the source table is routed to test_lightning_topsql.test instead of dtest.dtest_table. According to the source code, the router config is directly transmitted to the lightning unit, where the lightning router cannot recognize regular expression. This issue probably attributes to the PR #4358.
Versions of the cluster
DM version (run dmctl -V or dm-worker -V or dm-master -V):
(paste DM version here, and you must ensure versions of dmctl, DM-worker and DM-master are same)
Upstream MySQL/MariaDB server version:
(paste upstream MySQL/MariaDB server version here)
Downstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):
(paste TiDB cluster version here)
How did you deploy DM: tiup or manually?
(leave TiUP or manually here)
Other interesting information (system version, hardware config, etc):
>
>
current status of DM cluster (execute query-status <task-name> in dmctl)
(paste current status of DM cluster here)
The text was updated successfully, but these errors were encountered:
It seems intractable and unreasonable to introduce the dm's router to tidb's repo. What about adding a new package called regexpr-router to the tidb-tools repo?
It seems intractable and unreasonable to introduce the dm's router to tidb's repo. What about adding a new package called regexpr-router to the tidb-tools repo?
What did you do?
What did you expect to see?
migration succeeds. Designated tables are migrated to target table.
config:
What did you see instead?
In downstream database, the source table is routed to
test_lightning_topsql
.test
instead ofdtest
.dtest_table
. According to the source code, the router config is directly transmitted to the lightning unit, where the lightning router cannot recognize regular expression. This issue probably attributes to the PR #4358.Versions of the cluster
DM version (run
dmctl -V
ordm-worker -V
ordm-master -V
):(paste DM version here, and you must ensure versions of dmctl, DM-worker and DM-master are same)
Upstream MySQL/MariaDB server version:
(paste upstream MySQL/MariaDB server version here)
Downstream TiDB cluster version (execute
SELECT tidb_version();
in a MySQL client):(paste TiDB cluster version here)
How did you deploy DM: tiup or manually?
(leave TiUP or manually here)
Other interesting information (system version, hardware config, etc):
current status of DM cluster (execute
query-status <task-name>
in dmctl)(paste current status of DM cluster here)
The text was updated successfully, but these errors were encountered: