-
Notifications
You must be signed in to change notification settings - Fork 38
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
use patch_microbatch_end_time #307
Conversation
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide. |
1 similar comment
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide. |
9e72836
to
993f704
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-approving 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One suggestion, but non-blocking.
dbt-tests-adapter/dbt/tests/adapter/incremental/test_incremental_microbatch.py
Outdated
Show resolved
Hide resolved
…nimal Co-authored-by: Mike Alfare <[email protected]>
Closing this PR. We are first going to move the utility from dbt-core to dbt-common, then do this work |
resolves #N/A
docs dbt-labs/docs.getdbt.com/#
Problem
Usage of freezegun was not precise enough to just microbatch and caused issues in testing downstream in dbt-snowflake.
Solution
Use new utility to patch just microbatch end time introduced in dbt-labs/dbt-core#10713.
Checklist
Confirmed this fixes things in dbt-snowflake: https://github.com/dbt-labs/dbt-snowflake/actions/runs/10857121125/job/30133020922?pr=1179
Will need a patch release of dbt-test-adapters to get this out!