Describe the bug
The Databricks types GEOMETRY and GEOGRAPHY introduced in September are not supported by the materialization macro dbt_databricks.materialization_table_databricks. Hence, these types cannot be defined in the model definition, nor can the model contract be enforced.
Also reported on the dbt-fusion repo
Steps To Reproduce
- Define a
.sql model with a geometry/geography column
- Define geometry/geography as the
data_type in the model definition
- Run
dbt build on the test model
Expected behavior
geometry and geography should be accepted along existing data types.
Screenshots and log output
error: dbt1450: Error executing materialization macro 'dbt_databricks.materialization_table_databricks' for model model.dbt_xxx.xxxx: Serde JSON Error: unknown variant `geometry(25832)`, expected one of `tinyint`, `smallint`, `int`, `bigint`, `float`, `double`, `decimal`, `string`, `varchar`, `char`, `binary`, `boolean`, `date`, `timestamp_ltz`, `timestamp_ntz`, `interval`, `array`, `map`, `struct`, `variant`, `void` at line 1 column 2337
System information
The output of dbt --version:
dbt-fusion 2.0.0-preview.175
The operating system you're using:
Windows, X86
The output of python --version:
3.12
Describe the bug
The Databricks types
GEOMETRYandGEOGRAPHYintroduced in September are not supported by the materialization macrodbt_databricks.materialization_table_databricks. Hence, these types cannot be defined in the model definition, nor can the model contract be enforced.Also reported on the dbt-fusion repo
Steps To Reproduce
.sqlmodel with a geometry/geography columndata_typein the model definitiondbt buildon the test modelExpected behavior
geometryandgeographyshould be accepted along existing data types.Screenshots and log output
System information
The output of
dbt --version:The operating system you're using:
Windows, X86
The output of
python --version:3.12