-
Notifications
You must be signed in to change notification settings - Fork 28
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
Pass down schema on table creation #271
base: main
Are you sure you want to change the base?
Conversation
61d9820
to
82a7bbf
Compare
82a7bbf
to
442df41
Compare
The test cases around this don't seem to have that great coverage. I added two basic cases, but we might want to do some manual testing/extend these before merging. |
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.
Thank you for your PR!
Are you planning to add more test cases or you think we are ok with only 2 you provided?
Could you please also remove info logging? If you need them, you could change logging level to "debug".
kwargs = { | ||
"database": relation_parts[0], | ||
"schema": relation_parts[1], | ||
"identifier": relation_parts[2], | ||
"schema": ".".join(relation_parts[1:-1]), |
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.
What if there is no 1st element? and only zero one?
Summary
Description
There is no out-of-the-box way to configure dbt models materialised as tables to be created in subdirectories.
Test Results
Added tests to check the new behavior.
Changelog
Contributor License Agreement