New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
invalidate_hard_deletes=True directive does not work #37
Comments
- Fixed macro in snapshot.sql - Added a test case to test invalidation of hard deletes in snapshots
The fix is identified and currently the PR is in-review. I will let you know once we release this. Thank you, |
Hi @gbonazzoli This is fixed in dbt-oracle==1.1.2. We have also added a test case in our suite to test invalidation of hard deletes during dbt snapshots. You can install this version using
Please test this and let me know if you have any questions. |
Closing this issue. This was fixed in dbt-oracle==1.1.2. We have also added a test case in our suite to test invalidation of hard deletes during dbt snapshots. |
@aosingh, well done ! I confirm you that every things is now OK! Tested and used in production with the following software versions:
|
Is there an existing issue for this?
Current Behavior
If we have the following snapshot's confg:
and run
dbt snapshot
we obtain the following error:
Expected Behavior
No response
Steps To Reproduce
No response
Relevant log output using
--debug
flag enabledNo response
Environment
What Oracle database version are you using dbt with?
19c
Additional Context
none
The text was updated successfully, but these errors were encountered: