-
Notifications
You must be signed in to change notification settings - Fork 70
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
copydb Apply event Is not Autocommit ? #20
Comments
Hey. Can you post a log of the run and what replication event you found that was not replicated to the target? |
Here Is My Copydb Test Config, Source Mysql version perconae 5.6.23, Target 5.7.19 (gtid is ON) `{ "Target": { My Source Table before copy :
At Copying.... I delete some row at source table ...
But The Target t1 Table count Is:
I Consider Target Table count should be 22138 ~ Run Log & Not Cut over
|
And I Print apply sql At binlog_writer.go, But It's generated sql And print ok after |
What's your schema like? Do you have some example data for this rows? This can possibly help us build a test case. |
I found the problem,
It's not a null value, Lead to can't find that line when you delete it. |
@shuhaowu How to Deal it? |
I can't reproduce this issue using the docker compose servers that we spawn in local development (see docker-compose.yml for details). Are you sure your charset/collation settings are correct on both servers? Specifically, this is what I did:
|
I'm print the values in code: table stuct:
pirnt code:
runing ferry-copydb to migrate data.. on the source db execute: ferry-copydb stdout:
and you can get |
delete from tbo limit 1; Print Log:
|
Is your data actually just Please post a complete example with reproducing steps (a sql file to initialize the database would help) because I'm not sure how to try for this case. |
@shuhaowu Data generated in the test environment,It's No Problem when I Test another table the data from I Can't Generate Problem data at mysql shell,
And you load it,just ok |
I assume this is no longer a problem. |
I Found replication event Not apply on taget tables!
But I deug it print the apply sql!
The text was updated successfully, but these errors were encountered: