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

[explore] BigQuery DatabaseError surfaced as UnknownError with bad formatting #13155

Closed
mistercrunch opened this issue Feb 16, 2021 · 2 comments
Labels
explore:error Related to general errors of Explore good first issue Good first issues for new contributors inactive Inactive for >= 30 days

Comments

@mistercrunch
Copy link
Member

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)
Screen Shot 2021-02-16 at 8 02 26 AM

In SQL Lab, where it's better formatted
Screen Shot 2021-02-16 at 8 04 41 AM

@mistercrunch mistercrunch added the #bug Bug report label Feb 16, 2021
@junlincc junlincc added explore:error Related to general errors of Explore good first issue Good first issues for new contributors and removed preset-io #bug Bug report labels Feb 16, 2021
@stale
Copy link

stale bot commented May 2, 2022

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 .pinned to prevent stale bot from closing the issue.

@rusackas
Copy link
Member

rusackas commented Feb 5, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
explore:error Related to general errors of Explore good first issue Good first issues for new contributors inactive Inactive for >= 30 days
Projects
None yet
Development

No branches or pull requests

3 participants