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
The feature request is to fallback on using the BigQuery API directly for doing these mutations. Specifically, it should be possible to add columns to a nested type without dropping it.
The caveat is that adding columns to a nested type can only be done "at the end" (i.e.: STRUCT(foo, new_field, bar) is not possible, only STRUCT(foo, bar, new_field)).
Ideally, sqlmesh would allow appending fields to a STRUCT as long as the query also matches the resulting schema.
The text was updated successfully, but these errors were encountered:
This is a feature request for the BigQuery engine.
Currently, sqlmesh supports nested types (i.e.:
STRUCT
) within models, e.g.:It also supports changes to these, e.g.:
But because BigQuery does not support mutating nested types using SQL, the way this is implemented in sqlmesh requires dropping the column and creating a new one (which truncates the data).
The feature request is to fallback on using the BigQuery API directly for doing these mutations. Specifically, it should be possible to add columns to a nested type without dropping it.
The caveat is that adding columns to a nested type can only be done "at the end" (i.e.:
STRUCT(foo, new_field, bar)
is not possible, onlySTRUCT(foo, bar, new_field)
).Ideally, sqlmesh would allow appending fields to a
STRUCT
as long as the query also matches the resulting schema.The text was updated successfully, but these errors were encountered: