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
Describe the bug
When the target is Snowflake, if the staging view uses the datatype TIMESTAMP_TZ for the load_datetime and effective_from columns, then the ghost record generation fails with the following error:
17:00:24 001790 (42601): SQL compilation error:
17:00:24 inconsistent data type for result columns for set operator input branches, expected TIMESTAMP_TZ(9), got TIMESTAMP_NTZ(9) for expression [{2}] branch {3}
* Test passing for ghost record with hashdiff alias
* Add unit test for ghost record + hashdiff alias
Also move ghost record tests to correct folder
* Fix sat macro unit test failures
* Initial split of macro for cast_date and datetime
Re-produced #174
* TZ Test now passing for Snowflake
* Running on SQLServer, Postgres, BQ
* Fix SQLServer fixture
* Fix for postgres
Released v0.9.2, this should be fixed :) Please re-open if you continue to have the same issue, or open a new issue if you experience any new issues. Thank you for this report!
Describe the bug
When the target is Snowflake, if the staging view uses the datatype TIMESTAMP_TZ for the load_datetime and effective_from columns, then the ghost record generation fails with the following error:
Versions
dbt: 1.3.0
dbtvault: 0.9.1
target: Snowflake
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A satellite table should be created with a ghost record.
A work-around for now is to change the timestamp in the staging view to TIMESTAMP_NTZ.
The text was updated successfully, but these errors were encountered: