-
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
fix: Issue with on_schema_change config #273
Conversation
Hello,
Regards |
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 the contribution! I allowed the pipeline to run and it looks good. Could you also add a change to CHANGELOG.md
about this bug fix and add the test mentioned by @looping-aba please?
Changes have been made, I am in the process of setting up the test environment locally to make sure the newly added test case passes |
Just a small correction, the current version in development is |
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.
Looks good to me. Thank you for your contribution :)
@bcmeireles hang on, it looks like I have the test import wrong. Still working on the local setup, but it failed in CI |
- Moves the `raw_on_schema_change` variable back into scope for the config validator - Adds `BaseIncrementalOnSchemaChange` test to test_incremental.py resolves: dremio#268
Success after running
|
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.
This looks nice! Thank you for your contribution!!
@maladroitthief Hey! |
@howareyouman just signed it |
Summary
This fixes the on_schema_change config
Description
raw_on_schema_change
variable back into scope for the config validatorTest Results
Reproduced the bug described in #268, made changes to a local version of
dbt-dremio
and confirmed that it was behaving as expected.Changelog
Related Issue
resolves: #268