Ben Cassell
Ben Cassell
Should work already. Let me know if you hit any issues.
hmm, well I know we're using it in successfully in the model files: https://github.com/databricks/dbt-databricks/blob/3609a6ed5375848ea942036b2735fb6efc76101c/tests/integration/set_tblproperties/models/set_tblproperties.sql#L4. Could you try that and let me know if you get the same error?
Ok, so here's what's going on...it's yaml being weird. if you specify like this: ``` tblproperties: { "column.meta": "value" } ``` it should work (as opposed to the yaml expression...
> ```- "some_key": "geometry"``` I think this is the issue...sets the value of tblproperties to be an array with a dictionary as an entry, instead of: ``` tblproperties: "some_key" :...
I'm going to update the docs on dbt to include info on how to set tblproperties.
Thanks for raising this; I think we just didn't foresee that there would be integration over the dbt-databricks adapter :). Will speak with the product side about when we can...
Hmm, wonder why this wasn't reported sooner. This will be fixed soon when we upgrade materialized view behavior (hopefully next version if I've correctly fixed the too many 503 issues)....
Sorry for the delay, the beta with the fix is out today (1.8.0b1).
https://github.com/databricks/dbt-databricks/discussions/595
Thanks for filing this. Once the python config that I've been working on becomes part of a mainstream release, I will tackle this.