Closed carloVentrella closed 4 years ago
Hi, it is not easy to reproduce your case, could you please find a easier way to reproduce it? Then I can start to test and research it.
Maybe you can just construct the data that can reproduce the bug and decode it directly.
Closed for a while.
Hi, while using impyla to fetch results from impala, we faced a problem that seems related to the decode phase in thriftpy.
We're using version 0.4.11
When using the default batch_size (but we also tried with smaller ones), we see that thriftpy gets stuck while parsing the input buffer. I report the snippet from
binary.py
, enriched with some prints, useful during troubleshooting.We did some troubleshooting. The impala query is very simple:
We can see that thriftpy is able to decode many rows, then it blocks into
inbuf.read(sz)
. Interstingly, we noticed that the last payload reports some bytes that are not present in the original column.We see that a
\x00\x00\x00=
is being added to the original value.This is not a problem of the value itself, because the following query returns it correctly:
We also tried to run similar queries, but we got similar issue. I report the most significant. Before getting stuck we get:
Here there are no strange characters, but the value is not correct. In impala the value is the following:
It's not immediate, but in the print added inside thriftpy, there's a
a5-8
which is not present in the database.Do you have any idea of what can be the problem?
Thank you!