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

Remove assertion when there is an error in Presto #164

Merged
merged 1 commit into from
Oct 17, 2017

Conversation

timifasubaa
Copy link
Contributor

@timifasubaa timifasubaa commented Oct 4, 2017

The new schema for response_json in Presto 0.166 contains nextUri and this assertion prevents useful error messages in response['error'] from being propagated when errors happen. Instead it sends "Should not have nextUri if failed" which is not a useful error message.
@jingw

The new schema for response json contains nextUri and this assertion prevents useful error messages in response['error'] from being propagated when errors happen.
@mistercrunch
Copy link

For context please specify which version of Presto where the issue has been identified.

@codecov-io
Copy link

Codecov Report

Merging #164 into master will decrease coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #164      +/-   ##
==========================================
- Coverage   95.68%   95.68%   -0.01%     
==========================================
  Files          14       14              
  Lines        1415     1414       -1     
  Branches      146      146              
==========================================
- Hits         1354     1353       -1     
  Misses         40       40              
  Partials       21       21
Impacted Files Coverage Δ
pyhive/presto.py 93.61% <ø> (-0.05%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 437c7d6...14a9429. Read the comment docs.

@matthewwardrop
Copy link
Contributor

@jingw Greetings again!

Just pinging you about this PR in case you hadn't seen it. According to the official docs, insofar as you can call them that, the nextUri may or may not be present on any response, and one should just rely on the error field to determine whether there has been an error. As far as I can see there is no mention of nextUri being missing for errors. This is only masking error messages for true issues, so it is at least not preventing queries from succeeding, but it has made it hard to diagnose some users' issues.

Any chance you could consider merging this in soon?

@jingw
Copy link
Contributor

jingw commented Oct 17, 2017

lgtm, thank you! sorry for the delay.

@jingw jingw merged commit 19d7c2b into dropbox:master Oct 17, 2017
@matthewwardrop
Copy link
Contributor

Thanks @jingw !

@matthewwardrop
Copy link
Contributor

@jingw Would be great to get this pushed out in a point release if possible :).

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

Successfully merging this pull request may close these issues.

5 participants