Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

data validator with full mode don't support enum type #11300

Open
giant-panda666 opened this issue Jun 12, 2024 · 1 comment
Open

data validator with full mode don't support enum type #11300

giant-panda666 opened this issue Jun 12, 2024 · 1 comment

Comments

@giant-panda666
Copy link

What did you do?

  1. create table with enum column in upstream
  2. create full mode migration task which using full mode validator

What did you expect to see?

syncing and validating without error.

What did you see instead?

new of errorRowsStatus is increasing, and select from {task}_validator_error_change shows that type of enum data from binlog is int, but type of enum data from downstream is string.

Versions of the cluster

DM version (run dmctl -V or dm-worker -V or dm-master -V):

v7.5.1

Upstream MySQL/MariaDB server version:

5.7

Downstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):

v7.5.1

How did you deploy DM: tiup or manually?

tidb-operator

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)
@giant-panda666 giant-panda666 added area/dm Issues or PRs related to DM. type/bug This is a bug. labels Jun 12, 2024
@github-actions github-actions bot added this to Need Triage in Question and Bug Reports Jun 12, 2024
@fubinzh
Copy link

fubinzh commented Jun 17, 2024

/severity major

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

3 participants