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: failed to initialize the diff process with downstream MySQL and hidden column. #717

Closed
3AceShowHand opened this issue Apr 7, 2023 · 4 comments

Comments

@3AceShowHand
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.
set character_set_connection=utf8;

CREATE TABLE `t` (
  `pk` bigint(20) NOT NULL AUTO_INCREMENT,
  `j` json DEFAULT NULL,
  `i` int(11) DEFAULT NULL,
  `c` char(64) DEFAULT NULL,
  PRIMARY KEY (`pk`) /*T![clustered_index] CLUSTERED */
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin AUTO_INCREMENT=30001;

alter table t add index j((cast(j->'$.number[*]' as signed array))); 
  1. What did you expect to see?

sync diff runs normally

  1. What did you see instead?
[FATAL] [main.go:120] ["failed to initialize diff process"] [error="get table test.t's information error line 7 column 56 near \"'$.number[*]') as signed array)))\n) ENGINE=InnoDB AUTO_INCREMENT=30001 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin\"

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?
    sync-diff

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

@dveeden
Copy link
Contributor

dveeden commented May 24, 2024

@3AceShowHand this isn't a hidden column, but a generated column, right?

@dveeden
Copy link
Contributor

dveeden commented May 24, 2024

I have created #802 for hidden columns

@dveeden
Copy link
Contributor

dveeden commented May 24, 2024

Looks like you reported this for v7.0.0-1-g640ac78, but I can't reproduce this anymore on v8.1.0-1-g17af326

@dveeden
Copy link
Contributor

dveeden commented May 24, 2024

I can reproduce this on v7.0.0, so this was fixed somewhere after that release.

@dveeden dveeden closed this as completed May 24, 2024
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

No branches or pull requests

2 participants