We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Use dmctl binlog skip to skip a ddl error. For example, to skip errors when we add a not fully dropped column.
dmctl binlog skip
DM can sync following dml correctly.
DM reports error: schema mismatch dmls
DM version (run dmctl -V or dm-worker -V or dm-master -V):
dmctl -V
dm-worker -V
dm-master -V
v5.3.0
query-status <task-name>
(paste current status of DM cluster here)
The text was updated successfully, but these errors were encountered:
syncer(dm): track skipped ddls when using dmctl binlog to skip some d…
74a24d6
…dls (#4178) close #3239, close #4177
c95e582
…dls (#4178) (#4226) close #3239, close #4177
2a7ba40
…dls (pingcap#4178) close pingcap#3239, close pingcap#4177
520e2b0
…dls (#4178) (#4225) close #3239, close #4177
Successfully merging a pull request may close this issue.
What did you do?
Use
dmctl binlog skip
to skip a ddl error. For example, to skip errors when we add a not fully dropped column.What did you expect to see?
DM can sync following dml correctly.
What did you see instead?
DM reports error: schema mismatch dmls
Versions of the cluster
DM version (run
dmctl -V
ordm-worker -V
ordm-master -V
):v5.3.0
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: