kmarq

Wanted to drop some thoughts on the enforced component of contracts. Currently in order to use constraints you have to have a fully defined table to also enforce a contract....

> Python models are in fact the only models that are currently supported for running on job clusters, though its part of an on-going internal debate how much we want...

Just wanted to comment on this one. There's been lots of development on adding more constraint support and now custom constraints. However that's all blocked by requiring a contract even...

Thanks for the reply. From my understanding they are different in that the referenced ticket is still looking to fully contract a model (100% of fields defined) but allowing a...

That's good by me. Thank you

> If you want to define a table specification, you can't only define column constraints nor can you define a partial list of columns. So I'm not sure that what...

Recreated some previous testing of constraints. If you define a primary_key constraint on a column ``` columns: - name: col_1 data_type: string constraints: - type: not_null - type: primary_key ```...

Yeah, I see. I was definitely thinking Databricks centric and that we could do a merge with schema evolution enabled vs a straight insert. That would handle automatically adding extra_col....

The new one looks good, thank you. Happy to help with any other required discussion around potential options to implement this one. >For other warehouses we may need to do...

@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...