-
Notifications
You must be signed in to change notification settings - Fork 407
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: introduce CDC generation for merge operations #2747
Conversation
This is the beginning of the work but represents working `delete` `_change_type` information being produced on the merge operation
This does not have as much testing as it probably should, but preliminary results are looking good!
.and(col(TARGET_COLUMN).is_null()), | ||
)? | ||
.select(write_projection.clone())? | ||
.with_column(CDC_COLUMN_NAME, lit("insert"))?, |
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.
Why do we create inserts? Isn't it cheaper to let the cdf_reader calculate what was inserted?
Hmm so while checking this action, it seems our cdf_reader doesn't properly do this
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.
@rtyler I think we can add one optimization here, if we see it's insert only. So there is only a when_not_matched_insert_all statement, then we could avoid writing CDC as a whole.
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.
Nice work @rtyler 😄
it's been a slog y'all