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

[BigQuery] "500 Error encountered during execution. Retrying may solve the problem" from BigQuery should be raised as a DbtDatabaseError #11250

Open
Tracked by #11191
MichelleArk opened this issue Jan 28, 2025 · 0 comments
Labels
exceptions tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality

Comments

@MichelleArk
Copy link
Contributor

MichelleArk commented Jan 28, 2025

dbt compile
...
Runtime Error
  Runtime Error in test energy_est_year_avg (path/to/file.sql)
    500 Error encountered during execution. Retrying may solve the problem.; reason: backendError, message: Error encountered during execution. Retrying may solve the problem.

Exceptions like this are currently being raised as dbtRuntimeExceptions, when they should be DatabaseExceptions

@MichelleArk MichelleArk added exceptions tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality labels Jan 28, 2025
@MichelleArk MichelleArk changed the title [BigQuery] 500 Exceptions during dbt compile should be raised as Database Errors [BigQuery] "500 Error encountered during execution. Retrying may solve the problem" from BigQuery should be raised as a DatabaseException Jan 28, 2025
@MichelleArk MichelleArk changed the title [BigQuery] "500 Error encountered during execution. Retrying may solve the problem" from BigQuery should be raised as a DatabaseException [BigQuery] "500 Error encountered during execution. Retrying may solve the problem" from BigQuery should be raised as a DbtDatabaseError Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exceptions tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality
Projects
None yet
Development

No branches or pull requests

1 participant