-
Notifications
You must be signed in to change notification settings - Fork 430
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
feat: add schema evolution to merge statement #3136
base: main
Are you sure you want to change the base?
Conversation
fcc92b2
to
7f1b955
Compare
@JustinRush80 can you rebase your branch against main, or allow us to rebase it I will do thorough review tomorrow then :) |
6daa9ec
to
0a45cf0
Compare
@JustinRush80 could you rebase again, something went wrong since files changed is huge |
Signed-off-by: JustinRush80 <69156844+JustinRush80@users.noreply.github.com>
0a45cf0
to
53042d8
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3136 +/- ##
==========================================
+ Coverage 72.08% 72.27% +0.18%
==========================================
Files 134 134
Lines 43360 43757 +397
Branches 43360 43757 +397
==========================================
+ Hits 31258 31627 +369
- Misses 10085 10094 +9
- Partials 2017 2036 +19 ☔ View full report in Codecov by Sentry. |
Signed-off-by: JustinRush80 <69156844+JustinRush80@users.noreply.github.com>
.unwrap() | ||
.await | ||
.unwrap(); | ||
assert_eq!(metrics.num_target_files_added, 2); |
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.
@ion-elgreco any ideas why this assert is failing in the Ci pipeline but passing locally?
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.
Have you tried checking what the output is locally vs in the CI?
Description
Add schema evolution (only merge) to the MERGE statement. New columns are added based on the columns predicates in the MERGE operations (eg. target.id = source.id). Using when_not_matched_insert_all and when_matched_update_all will add any new column to the target schema
Related Issue(s)
Documentation