Closed mjahammel closed 1 year ago
We ran into this one as well. This is a deal breaker from us using this feature at the moment.
We ran into this one as well. This is a deal breaker from us using this feature at the moment.
Hotfix on its way!
Thank you sir!
On Thu, Dec 22, 2022 at 6:21 AM Alex Higgs @.***> wrote:
We ran into this one as well. This is a deal breaker from us using this feature at the moment.
Hotfix on its way!
— Reply to this email directly, view it on GitHub https://github.com/Datavault-UK/dbtvault/issues/173#issuecomment-1362897003, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXEQEAZ6UWRP52FKOATHSP3WORPXVANCNFSM6AAAAAATDSHWLY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
--
Chris Puuri
Healthcare & Data Engineering Lead
@.***
+1.619.884.5183 | Meet With Me https://meetings.hubspot.com/christopher-puuri
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 hashdiff column for a satellite is specified with an alias, the ghost record generation fails with an error like so:
Examining the generated code shows that the 'ghost' CTE has not included the hashdiff column, resulting in the error.
Versions dbt: 1.3.0 dbtvault: 0.9.1 Target: Snowflake
To Reproduce Steps to reproduce the behavior:
Expected behavior The satellite should be created with a ghost record included.