-
Notifications
You must be signed in to change notification settings - Fork 14.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
[explore] BigQuery DatabaseError surfaced as UnknownError with bad formatting #13155
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue |
This is likely fixed by now, and is pretty out of date if not. Closing this as stale since it's been silent for so long, and we're trying to steer toward a more actionable Issues backlog. If people are still encountering this in current versions (3.x) please open a new Issue or a PR to address the problem. |
BigQuery error is hard to read.
Expected results
In Explore, when creating a bad expression (say
DATE_TRUNC(column_that_dont_exist, DAY)
) in BigQuery, the DatabaseError is shown as a UnknownError. In SQL Lab, DatabaseErrors are surfaced properly and make sure to use a monospace font so that the formatting is preserved. For most database, the formatting doesn't matter much, but for BigQuery it's important to preserve it.Screenshots
In explore (where the issue shows)
In SQL Lab, where it's better formatted
The text was updated successfully, but these errors were encountered: