-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
presto error messages are hard to read #1529
Comments
Note, an easy "fix" is to patch
to pull our the error message. Then you get error messages like: That feels kinda hacky though -- maybe there's a reason the fuller blob is being sent? If not, I can put together a PR that makes this change. |
This definitely looks nicer! But I agree that the implementation feels hacky. The snippet you posted on what line in preto.py does it belong? |
Maybe to make it less hacky we catch a more specific exception class there rather than just |
Thanks @aslotnick ! Merged. |
Thank you, @arikfr ! Happy to finally contribute. |
Issue Summary
Errors for the presto query runner produce a hard-to-read stringified JSON blob, e.g.:
It'd probably be useful to just have the embedded message field instead of the entire thing -- the JSON escaping and and Presto stack trace are rarely relevant to the user.
Steps to Reproduce
Technical details:
The text was updated successfully, but these errors were encountered: