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

sync-diff will not report error when upstream has table but downstream doesn't #583

Closed
lance6716 opened this issue Dec 31, 2021 · 1 comment · Fixed by #548
Closed

sync-diff will not report error when upstream has table but downstream doesn't #583

lance6716 opened this issue Dec 31, 2021 · 1 comment · Fixed by #548

Comments

@lance6716
Copy link
Collaborator

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
    If possible, provide a recipe for reproducing the error.

upstream has all_mode.t2 and t1, downstream has all_mode.t2

  1. What did you expect to see?

error: table all_mode.t1 does not exists in downstream

  1. What did you see instead?
$ bin/sync_diff_inspector --config ~/Projects/ticdc/dm/tests/all_mode/conf/diff_config.toml
A total of 1 tables need to be compared

Comparing the table structure of ``all_mode`.`t2`` ... equivalent
Comparing the table data of ``all_mode`.`t2`` ... equivalent
_____________________________________________________________________________
Progress [============================================================>] 100% 0/Progress [============================================================>] 100% 0/0
A total of 1 table have been compared and all are equal.
You can view the comparision details through '/tmp/ticdc_dm_test/output/sync_diff.log'
  1. What version of TiDB are you using (tidb-server -V or run select tidb_version(); on TiDB)?

  2. which tool are you using?

  3. what versionof tool are you using (pump -V or tidb-lightning -V or syncer -V)?

@lance6716
Copy link
Collaborator Author

need revert pingcap/tiflow#3413 after this is fix

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

Successfully merging a pull request may close this issue.

1 participant