-
Notifications
You must be signed in to change notification settings - Fork 1.3k
gh-ost Error 1366: Incorrect string value modify charset #1249
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
Comments
We are encountering the same issue as above when changing collation to utf8mb4, is there a workaround for this? |
If I'm not mistaken, this error appears because the data contains char windows_1252 \x80-\xFF. if I convert char to hex, there is a difference between latin1 and utf8.
|
It looks like a fix may have been done for this (which was merged to master in September 2022) - #1158 - but there has not been a release including this fix since then. |
ah that's right, I've tried it for a small table, which has a size of ~2GB, and no problem appears. but for a large table with a size of ~70GB, I got an error |
We got ours to work using a different SQL statement in the gh-ost query, maybe try the following and see if it also works for you.
|
still error, if the column contains one of \x80-\xFF |
I can also confirm that we encounter the issue when the table size is large, it currently fails on a ~900GB table we are attempting to do a migration on. 😢 If I take the offending row that it fails on and add to a temp table, then gh-ost runs and completes correctly. |
@jondrummond-codeo / @atanthowiz if possible, could you test on |
I'm currently using this branch. previously I ran gh-ost with chunk-size=100 on high traffic and tried it also on low traffic, but always got error updated: |
It has nothing to do with traffic and chunk-size. It may occurs , when an illegal latin1 character (such as windows_1252 \x80-\xFF) was inserted in a transaction just during changing the table. |
Thanks @wangzihuacool - I see that #1158 was merged to master last year September, is there a plan to get this into a release any time soon or should we clone master and do the build ourselves to get around this? |
I think this case is already solved. |
Hi,
I tried to run gh-ost to modify charset in specific column of table. Eventually it failed with a message like this
for my table definition:
and this one for gh-ost command :
I have tried the gh-ost with latest version (1.1.15), v1.1.2, and v1.0.48, but that doesn't solve the problem. I dont know this is related to this issue 267 or not, but that issue solved with v1.0.21. but I can't use v1.0.2 since I using gcp and in v1.0.2 the -gcp flag is not available.
Thank you!
The text was updated successfully, but these errors were encountered: