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

error occurred when the different row's json column is NULL in the one db source, but is not NULL in the other db source #736

Closed
Leavrth opened this issue Aug 21, 2023 · 0 comments · Fixed by #737

Comments

@Leavrth
Copy link
Contributor

Leavrth commented Aug 21, 2023

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?

upstream:

create database if not exists json_test;
create table json_test.test (a int, b json, primary key(a));

insert into json_test.test values (1, '{"id": 1, "name":"aaa"}');

downstream:

create database if not exists json_test;
create table json_test.test (a int, b json, primary key(a));

insert into json_test.test values (1, NULL);
  1. What did you expect to see?
    check different

  2. What did you see instead?
    error occurred:

Error in comparison process:
unmarshal json  failed, error unexpected end of JSON input error occured in `test`.`t`
  1. What version of TiDB are you using (tidb-server -V or run select tidb_version(); on TiDB)?
    master
  2. which tool are you using?
    sync-diff-inspector
  3. what versionof tool are you using (pump -V or tidb-lightning -V or syncer -V)?
@Leavrth Leavrth changed the title error occurred when the different row's float column is NULL in the one db source, but is not NULL in the other db source error occurred when the different row's json column is NULL in the one db source, but is not NULL in the other db source Aug 21, 2023
@ti-chi-bot ti-chi-bot bot closed this as completed in #737 Aug 21, 2023
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