-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[Regression] show
command should more gracefully handle/fail queries that fail to execute
#9946
Comments
show
command should more gracefully handle/fail queris that fail to executeshow
command should more gracefully handle/fail queris that fail to execute
show
command should more gracefully handle/fail queris that fail to executeshow
command should more gracefully handle/fail queries that fail to execute
@dataders are you still seeing this issue in dbt 1.7 or 1.8? I wasn't able to reproduce this with Python 3.10.10 and the same versions of dbt-core and dbt-snowflake as you -- here's what I got instead:
|
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days. |
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers. |
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers. |
Describe the feature
I'm noticing that #8166 is happening again on
dbt-core==1.7.11
with multiple adapters.If as user calls
dbt show
on a model or inline-query that the underlying data platform does not like, dbt should quit and return the database error. Instead, show continues, which results in an stack trace resulting from dbt trying to callAgate.Table.print_table()
on aNone
.The undesirable behavior is consistent across both the
--inline
and-s some_model
usage patterns.Reproducible Example
input
output
Describe alternatives you've considered
Perhaps there's a
try-catch
that if there's a database error and noResultSet
is returned, thendbt show
can return/print an empty Agate table? or even a table with the database error in it?Who will this benefit?
All users of
dbt show
as well as users of downstream tools that make use of the same.Are you interested in contributing this feature?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: