-
Notifications
You must be signed in to change notification settings - Fork 682
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
Json length is larger than packet length #398
Comments
I have the same problem |
i have the same problem too. |
in my case, #403 , no error is returning to program, but cpu goes up to 100% for the all time. have no idea if there is any connection with this issue. |
@nankingrider I checked your issue. This issue is not long json value, is a very rare case. In my binlog dump case, MySQL 8.0 are jump the junk data. but |
@jongwony Hi , thanks for the reply.!
a reasonable guess is maybe mysql generate junk data when json type field is too long ... still trying to figure how to fix it. |
@jongwony @channss @xufei4987 I need your Many test cases. |
environment: MySQL 8.0
python: 3.11.1
Hexdump
Above hexdump data
@4
is very long JSON type value, I think the error occurs because it doesn't properly recognize the large JSON.Traceback
I am working hard on debugging myself with ipdb debugger., but I would like to share it would be nice to get help in understanding the hexdump.
Looking at
out
, it seems that the parsing is not going well.I've been running this environment for quite some time. For small JSON s this was fine.
The text was updated successfully, but these errors were encountered: