Database ... not found
error terminating run on spark clusters
#277
Labels
bug
Something isn't working
Database ... not found
error terminating run on spark clusters
#277
Describe the bug
Due to a recent fix #270 - this is terminating runs on spark clusters when it previously wasn't (
dbt-databricks==1.4.1
)Note that in typical fashion, dbt will build the relation cache at the start of the run via some
show databases
/show tables in ...
queries - so I don't think the issue here is that dbt is runningshow ...
but rather an error (that was the result of ashow ...
query) previously did not cause the run to terminate but now does.Steps To Reproduce
dbt-databricks==1.4.2
build only one of the models.dbt-databricks==1.4.1
and rerun the same command above:Expected behavior
There should be consistent behaviour between
dbt-databricks==1.4.2
anddbt-databricks==1.4.1
wherein models are built even if a database is not found.Debug log output
dbt-databricks==1.4.2
dbt-databricks==1.4.1
System information
The output of
dbt --version
:The operating system you're using:
macOS
The output of
python --version
:Additional context
Note that there is no issue if not using SQL endpoints instead:
Notably the errors returned are different between spark clusters and SQL endpoints for the same error.
The text was updated successfully, but these errors were encountered: