Skip to content
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

Can't get results from fetches #38

Open
aub opened this issue Sep 1, 2015 · 3 comments
Open

Can't get results from fetches #38

aub opened this issue Sep 1, 2015 · 3 comments

Comments

@aub
Copy link

aub commented Sep 1, 2015

I'm connecting to a spark-sql thrift server, which supports the HiveServer2 protocol. When I make queries using fetch, I can see that the data is returned, but it is in fetch_results.results.columns rather than fetch_results.results.rows, so the code always returns an empty array. Is this a known issue? Perhaps it's only a problem for spark-sql? I'd be happy to submit a patch, but it's unclear from some of the comments here if the gem is currently working for queries.

@lloydpick
Copy link
Member

This is probably related to the columnar data return, rbhive doesn't currently support this behaviour correctly. You can try setting the hive_version to 12 when you connect and that might solve your problem. I can't test this myself unfortunately.

@aub
Copy link
Author

aub commented Dec 1, 2015

Yep, confirmed that using version 12 works. Thanks.

On Tue, Dec 1, 2015 at 3:11 PM, Lloyd Pick [email protected] wrote:

This is probably related to the columnar data return, rbhive doesn't
currently support this behaviour correctly. You can try setting the
hive_version to 12 when you connect and that might solve your problem. I
can't test this myself unfortunately.


Reply to this email directly or view it on GitHub
#38 (comment).

@pyro2927
Copy link

Have the same issue when running hive 0.13, need to specify hive_version: 12 in the connection. @lloydpick is this on a roadmap to be fixed, or can you point to the code in where the problem may lie? I wouldn't mind attempting to giving it a go in fixing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants