You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues, and I could not find an existing issue for this feature
I am requesting a straightforward extension of existing dbt-snowflake functionality, rather than a Big Idea better suited to a discussion
Describe the feature
As Iceberg tables in Snowflake do not support semi-structured data types (e.g. ARRAY, OBJECT, etc), in order to have full support for Snowflake Iceberg tables in dbt we also need structured data types to be supported (details on Iceberg data types here and on structured data types here).
In the current implementation of the adapted, I'm not able to use these data types, getting the error:
Could not interpret data_type "ARRAY(VARCHAR(16777216))": could not convert "VARCHAR(16777216" to an integer
This issue is similar to what was previously reported for vector types here.
Describe alternatives you've considered
No response
Who will this benefit?
Everyone trying to create Snowflake Iceberg tables using dbt.
Are you interested in contributing this feature?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is this your first time submitting a feature request?
Describe the feature
As Iceberg tables in Snowflake do not support semi-structured data types (e.g.
ARRAY
,OBJECT
, etc), in order to have full support for Snowflake Iceberg tables indbt
we also need structured data types to be supported (details on Iceberg data types here and on structured data types here).In the current implementation of the adapted, I'm not able to use these data types, getting the error:
This issue is similar to what was previously reported for vector types here.
Describe alternatives you've considered
No response
Who will this benefit?
Everyone trying to create Snowflake Iceberg tables using dbt.
Are you interested in contributing this feature?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: