Sources ignore default catalog 1.7.4 previously was working about dbt-databricks HOT 4 OPEN

Thanks for the report, will investigate.

from dbt-databricks.

Can you validate, do you have this same problem with 1.7.3? I think I know the cause, but getting that additional data point would help significantly. I'm pretty sure this is related to changes we had to make in 1.7.0 due to catalog and schema becoming non-optional on Credentials, so if that is the issue (in which it would also repro on 1.7.3), the fix might be a little involved.

from dbt-databricks.

@benc-db Unfortunately it looks like DBT Cloud only let's me select the major version and won't let me specify a minor version. Not seeing anything in the docs that I can use to override that.
We have a workaround in place now by specifying the catalog explicitly, but may want to make sure that this scenario is noted in the upgrade notes.
Also, I see 1.7.4 of the dbt-databricks releases is marked pre-release now, but looks like DBT Cloud is still pulling it in. Not sure if there is something required between Databricks and DBT to coordinate rollback items like this.
From triggering a run just now to confirm:
16:49:13 Registered adapter: databricks=1.7.4

from dbt-databricks.

Yeah, unfortunately there is required coordination. 1.7.4 has been pulled because it does not play nicely with cold-starting non-serverless SQL Warehouses. Working on fixing that at high priority so that next week dbt Cloud can pick up a good version.

from dbt-databricks.