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-inspector : don't compare the partition attribute of schema #739

Open
knull-cn opened this issue Sep 15, 2023 · 2 comments · May be fixed by #832
Open

sync-diff-inspector : don't compare the partition attribute of schema #739

knull-cn opened this issue Sep 15, 2023 · 2 comments · May be fixed by #832

Comments

@knull-cn
Copy link

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.
    compare the schema, partition table, different partitions of upstream and downstream
# upstream
create table t(c1 int, c2 int) partition by hash(`c1`) partitions **11**;
# downstream
create table t(c1 int, c2 int) partition by hash(`c1`) partitions **5**;
  1. What did you expect to see?
    Show the different table list, we can find the t

  2. What did you see instead?
    We can not find the table t in different table list

  3. What version of TiDB are you using (tidb-server -V or run select tidb_version(); on TiDB)?
    v6.5.2

  4. which tool are you using?
    sync-diff-inspector

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

@dveeden
Copy link
Contributor

dveeden commented May 24, 2024

cc @mjonss

@dveeden
Copy link
Contributor

dveeden commented May 24, 2024

Still an issue with:

$ ./bin/sync_diff_inspector -V
App Name: sync_diff_inspector v2.0
Release Version: v8.1.0
Git Commit Hash: a005a9426f5bd82664907b97344f4255fc8608b1
Git Branch: HEAD
UTC Build Time: 2024-05-24 09:26:23
Go Version: go1.22.3

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.

2 participants