-
Notifications
You must be signed in to change notification settings - Fork 234
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
Supports new error messages. #520
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all seems like a reasonable change to me
@ueshin seems the change you made for the tuple may of introduced something |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great work @ueshin this looks like a good early change.
* Supports new error messages. * changie * tuple * fix. * suggestion.
* manual backport/modifcation of #520 to mergable to 1.1.latest * returning to older style call in logic Co-authored-by: Takuya UESHIN <ueshin@databricks.com>
resolves #515
Description
Supports new error messages.
In
SparkAdapter.get_columns_in_relation
, it checks the error message when the specified table or view doesn't exist:dbt-spark/dbt/adapters/spark/impl.py
Line 223 in c87b6b2
but, Spark will change the error message in the future release (apache/spark#37887), which causes the function to raise the
dbt.exceptions.RuntimeException
instead of returning an empty list.The function should also check whether the error message contains
[TABLE_OR_VIEW_NOT_FOUND]
or not.Checklist
changie new
to create a changelog entry