- Notifications
You must be signed in to change notification settings - Fork1.6k
BigQuery: fix swallowed error message#6168
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
When getting a "Cannot query over table (...) without a filter overcolumn(s) (...)", the re-raising happening gobbles up the error messageand the context is lost.This may or may not be the right fix, but clearly highlights the issueof `self._query_job.errors` being `None` in that particular context.When that is the case, the only context available is that of`DatabaseError` without any details which clearly isn't enough detail.It seems like wrapping the exception into another exception works asexpected and shows both stack traces as shown here:
googlebot commentedOct 4, 2018
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝Please visithttps://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here (e.g. What to do if you already signed the CLAIndividual signers
Corporate signers
|
sumedhsakdeo commentedOct 4, 2018
Looks great. CC:@tswast |
| exceptgoogle.cloud.exceptions.GoogleCloudError: | ||
| raiseexceptions.DatabaseError(self._query_job.errors) | ||
| exceptgoogle.cloud.exceptions.GoogleCloudErrorase: | ||
| raiseexceptions.DatabaseError(self._query_job.errorsore) |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading.Please reload this page.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading.Please reload this page.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading.Please reload this page.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading.Please reload this page.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading.Please reload this page.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading.Please reload this page.
The errors on the job resource are mostly redundant with the exception information.
googlebot commentedOct 10, 2018
CLAs look good, thanks! |
mistercrunch commentedOct 13, 2018
🔥 🕺 🔥 |
When getting a
Cannot query over table (...) without a filter over column(s) (...), the re-raising happening gobbles up the error messageand the context is lost.
This may or may not be the right fix, but clearly highlights the issue
of
self._query_job.errorsbeingNonein that particular context.When that is the case, the only context available is that of
DatabaseErrorwithout any details which clearly isn't enough detail.