-
Notifications
You must be signed in to change notification settings - Fork 94
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
0.4.14 maximum query size #162
Comments
it may be caused by #158, could you please try to install the master branch of thriftpy2? |
Hey ethe, |
not 0.4.14, please install the master branch directly from the source code, the fixed code of #158 is not released yet, but if you could make a quick verification. |
Hey Ethe, a colleague of mine has tested it with commit 108cca5, and the error still persists and we get the same error as before. here is the stacktrace:
|
We also found this online, that has the same issue as us: cloudera/thrift_sasl#28 |
Thanks for pointing this out @Rosadosa. Yes my issue appears to be the same. Are you also using thrift-sasl? It still isn't clear to me which library is the issue, as the debug stack trace I got (linked in the thrift-sasl issue) calls both of them just before erroring. I tried thriftpy2==0.4.14, 0.4.12, 0.4.11, and also thriftpy2@master from github, and I still had the same issue with all of them. The only way I can get it to work is by using thrift-sasl==0.2.1, which uses thriftpy, not thriftpy2, which again means it could be a problem with either of them. Using thrift-sasl==0.2.1 is not a good solution though because thriftpy is deprecated and it doesn't install right on Python 3.7+. |
hi @Maxsparrow @Rosadosa could you please give me a test case to reproduce this issue? |
Sure, this is what I run against our kerberized Impala cluster to reproduce the problem: Python 3.7
Error:
Full debug stack trace is available in the linked thrift-sasl ticket - do you want me to copy it here? Using LIMIT 1 instead of LIMIT 1000 works. As @Rosadosa noted, there is a certain size where it stops working (they said 15kB, but I didn't test to find the exact amount). I've tried a variety of other things like using cursor.fetchone() instead of fetchall(), but I get the same issue. Impala daemon logs make it look like a normal successful query. |
@Maxsparrow Sorry I am not familiar with samba or thrift-sasl, maybe it is better to have more exactly info to point out that it is caused by thriftpy2. |
Hi @ethe, from the other ticket, the debug stack trace shows that thriftpy2 throws a timeout:
I don't really know how to read this though. Do you have any ideas as to why it would timeout? |
We encountered an issue using this package together with impyla to query to a Hive data base in a Cloudera stack.
When firing of the query with impyla it arrived at the cluster and was executed.
However, we did not receive the results back and we got a impala.error.HiveServer2Error: Invalid query handle: error.
We found out by trial and error that when we put a limit on our query we were able to retrieve data with a maximum size of 15kB.
The issue was resolved by installing thriftpy2 version 0.4.12, so it seems something in 0.4.14 is causing this issue.
We used impyla version 1.16.3.
The text was updated successfully, but these errors were encountered: