-
Notifications
You must be signed in to change notification settings - Fork 3k
API: Fix Transform backward compatibility in PartitionSpec #6653
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
Conversation
amogh-jahagirdar
left a comment
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.
@deniskuzZ Thanks for the contribution! when you get a chance could you update the PR description about what the incompatibility issue (or if there's a github issue a link to that) is and why this change is required?
|
@amogh-jahagirdar, thanks for checking! updated PR description and added unit test |
|
I also had a workaround for this issue, see #6482. Not sure which way is more reasonable. |
Understood. I am ok with either solution too. Hope to fix this as soon as possible to unblock the Hive-iceberg upgrading. |
|
@Fokko could you please take a look |
|
hi @pvary, could you please help with the review? |
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.
Sorry for the late reply, I was traveling the last few days. I like this solution. It is until Iceberg 2.0.0 that we have to keep the lazy and non-lazy versions of initializing a PartitionSpec using a transform.
Thank you! |
BaseUpdatePartitionSpec::addField is failing with “Cannot add duplicate partition field” for the re-added DATE type field.
existing.transform().equals(sourceTransform.second()) returns FALSE since the types are different:
Test