-
Notifications
You must be signed in to change notification settings - Fork 414
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: delta scan partition ordering bug #1789
Conversation
take |
@mightyshazam @MrPowers Why is there a take on this PR? it's mostly done the only things that needs to be done is removing some unwraps. |
@Blajda - sorry for the miscommunication. @mightyshazam will help out with a review. I assigned it to him cause I can't assign him as a reviewer, but now realize that was misleading. So yea, let @mightyshazam know when you're done so he can take a look, thanks!! |
@MrPowers |
@mightyshazam this is ready for review. Thanks for taking the initiative |
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. I pointed out a pretty trivial optimization to take or leave.
Description
Sometimes the order of partition columns in our delta schema does not match the order of partition columns in the deltatable metadata.
This would cause
DeltaScan
to provide incorrect values for partition columns.This is fixed by having
DeltaScan
use the metadata as the source of truth.Related Issue(s)
MERGE
works incorrectly with partitioned table if the data column order is not same as table column order #1787