-
Notifications
You must be signed in to change notification settings - Fork 7
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
DONT APPROVE BEFORE 55! 0.9.9.1 - test_overwrite per column instead of model and fk at_least_one #57
Merged
LewisCharlesBaker
merged 19 commits into
master
from
amir_feb23_test_overwrite_not_all_columns/0.1.0
Feb 22, 2023
Merged
DONT APPROVE BEFORE 55! 0.9.9.1 - test_overwrite per column instead of model and fk at_least_one #57
LewisCharlesBaker
merged 19 commits into
master
from
amir_feb23_test_overwrite_not_all_columns/0.1.0
Feb 22, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
trying to bug fix droughty dbt error "UserWarning: You have an incompatible version of 'pyarrow' installed (6.0.0), please install a version that adheres to: 'pyarrow<8.1.0,>=8.0.0; extra == "pandas"'"
LewisCharlesBaker
approved these changes
Feb 13, 2023
@Terroface - This looks great. @jack @jordan, we have some customer projects we could update to this method and we'll need to once this is shipped |
Terroface
changed the title
0.9.5 - test_overwrite per column instead of model and fk at_least_one
0.9.7 - test_overwrite per column instead of model and fk at_least_one
Feb 21, 2023
wait to approve this until #55 is approved and merged into this |
Terroface
changed the title
0.9.7 - test_overwrite per column instead of model and fk at_least_one
DONT APPROVE BEFORE 55! 0.9.7 - test_overwrite per column instead of model and fk at_least_one
Feb 21, 2023
Terroface
changed the title
DONT APPROVE BEFORE 55! 0.9.7 - test_overwrite per column instead of model and fk at_least_one
DONT APPROVE BEFORE 55! 0.9.9.1 - test_overwrite per column instead of model and fk at_least_one
Feb 22, 2023
…23_test_overwrite_not_all_columns/0.1.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
test_overwrite
now only affects the columns specified instead of overwriting all the columns for their modelfk
columns is nowdbt_utils.at_least_one
Reasoning
test_overwrite
change: Suggestion: don't make test_overwrites overwrite all columns for model #51at_lest_one
change: revert to default 'at_least_one' test on foreign keys #50Considerations
Files changed
section