Ben Cassell
Ben Cassell
Thanks for reporting. There is currently a PR for improving column comment materialization, I will check with author if it addresses this issue.
Ok, #750 didn't fix this particular issue so we'll need to dig deeper into what changed. Thanks for reporting.
This is a legit bug that we aim to fix shortly, but what's surprising to me is the idea that it was introduced in 1.8...I'm reasonably sure we had this...
When it's fixed you will have the option of either using Databricks OAuth secret, or AAD secret. The reason it could work in old versions of 1.7.x is we didn't...
So, long story short, I'm working on some stability work right now (ensuring that new versions of the Databricks runtime don't break dbt users), and the next thing I'll work...
Hi apologies for the long delay. We had been waiting on a fix in the Databricks SDK, which I believe has landed. Now I'm waiting for @eric-wang-1990 (my OAuth expert...
This is because our path for executing sql does not allow executing multiple statements separated by `;`. This is a Databricks limitation, rather than a dbt limitation. I believe that...
The flip side though is that you can put them into hooks as separate entries: ``` "on-run-start": [ "", "" ] ```
What is the advantage of doing it this way, over using Databricks Workflow with dbt task type?
I'm reasonably certain that we don't actually support clone as a materialization, but as support for [dbt clone](https://docs.getdbt.com/reference/commands/clone)