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
It is unintuitive that when a user requests data to be replicated into schema (or dataset in BQ) X that we replicate it into schema X_NORMALIZED. We should replicate the normalized table into X.
The text was updated successfully, but these errors were encountered:
DBT is not able to overwrite the destination table that contains the JSON blob data with a new table with the proper schema since it is using that JSON BLOB as input. (Same table is simultaneously used as input and output)
So the destination connectors should write into a different table name instead (with a _raw suffix?) so that DBT can actually output the final destination table name with the proper normalized schema.
Currently to bypass this problem, DBT is writing in a different schema that has a _NORMALIZED suffix
Tell us about the problem you're trying to solve
It is unintuitive that when a user requests data to be replicated into schema (or dataset in BQ)
X
that we replicate it into schemaX_NORMALIZED
. We should replicate the normalized table intoX
.The text was updated successfully, but these errors were encountered: