-
Notifications
You must be signed in to change notification settings - Fork 180
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
'utf-8' codec can't decode byte #493
Comments
I tried to debug the issue, I check the value of fetched bytes on working and bugged host.
If I blindly overwrite the value |
Hi @azdobylak, I have no clue based on your description, and I cannot reproduce the problem in my environment.
|
|
You should receive RowDescription(type: b'T'), DataRow(type: b'D'), CommandComplete(type: b'C') messages in order. It seems to be not a problem of vertica-python, but a problem of either your environment or the server. If you still see such error in your upgraded dev environment, please leave your OS info, python version, server version (x.x.x-x), I'll report this to the server team. |
The workaround is published in vertica-python v1.3.2. In the meantime, anyone hit this problem are welcome to report their error details here, we'd like to collect as much info as possible to fix this server bug. v1.3.2 will issue a warning message if you hit this issue, you can share that warning in this thread. |
|
I also got the same error on the version 1.3.2 |
Server version 12.0.4-3 has the full fix now. Please upgrade your server to fix this issue. |
@sitingren Did you mean Vertica to version 12.0.4-3 right? |
@chathawee Yes |
After migration to Vertica 12.0.3 (from 12.0.1) I have an issue with decoding messages. I am using cluster with 3 nodes, running query on 3rd node returns an error:
At the same time the query executes correctly on 1st and 2nd node. The issue also occurred on 2nd node, and for some time worked on 3rd node.
The issue was spotted only with vertica_python, it works fine with pyodbc and vsql, so I suppose it is possible to improve response handling. I'm using
vertica_python==1.3.1
. To exclude network issue I reproduced the issue on the server (executed the script locally), the error was the same.The text was updated successfully, but these errors were encountered: