Doug Beatty

Thanks for reaching out @ivan-fishbrain ! This is expected behavior, so I switched this from a bug report to a feature request.

@cla-bot check

Thanks for reaching out @thuymo87. Could you share a simple set of dbt project files to help us try to reproduce the issue you are seeing? That way we can...

Glad to hear that you were able to get it to work (even it it required downgrading to Python 3.11). Our [Python compatibility matrix](https://docs.getdbt.com/faqs/Core/install-python-compatibility#python-compatibility-matrix) indicates that v1.8 supports Python 3.12,...

Thanks for providing that detail, Mo. I tried to reproduce the error you got by switching to Python 3.12.3 using `pyenv` and then installing dbt-databricks~=1.8.0, but I wasn't able to...

@yengibar-manasyan-sp did you try [this](https://docs.getdbt.com/reference/resource-properties/unit-test-input) to expect empty output? ```yaml expect: rows: [] ```

An alternative: What if `target_schema` / `target_database` were just treated as aliases of `schema` / `database`? This would have the double advantage of building in the place you intended without...

>I think we need to maintain `target_schema` and `target_database` for backwards compatibility @graciegoheen that aligns with what I'm saying: treat `target_schema` / `target_database` as valid options within YAML snapshots. We'd...

@MichelleArk What would be the next steps to determine if we can adopt the change in this PR or not? Do we know of any other key assumptions that would...

Thanks for reaching out about this @rickscarta! After taking a look, I think this is actually the expected behavior. Details in the "digging in" section below. Out of curiosity, does...