-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[dagster-dbt][fix] use standalone duckdb dbfile for row count test #21852
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @benpankow and the rest of your teammates on Graphite |
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.
See comment, but 🙏
it, rather than using the default one-file-per-worker approach. | ||
""" | ||
jaffle_shop_duckdb_db_file_name = "cool_jaffle_shop" | ||
jaffle_shop_duckdb_dbfile_path = f"target/{jaffle_shop_duckdb_db_file_name}.duckdb" |
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.
Should probably parameterize this by the test name to guarantee isolations between tests
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.
had this initially but changed it to test something and forgot to change it back 😅 , thanks
Summary
Fix for flaky dagster-dbt test which uses a standalone duckdb file for the row count test, to control for duckdb holding the file lock.
Replaces #21763
Test Plan
bk