-
Notifications
You must be signed in to change notification settings - Fork 3k
Core : Fixing allowed null values for iceberg table properties #3052
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
Core : Fixing allowed null values for iceberg table properties #3052
Conversation
4f7a7fc to
faaba1d
Compare
faaba1d to
19b11df
Compare
|
Thanks, @rawataaryan9! Looks good. I approved this to run tests and I'll merge when they pass. |
kbendick
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.
LGTM
|
Merged. I'm also marking this for inclusion in a patch release if we decide to make one. While it probably isn't reason in itself to do another release, it would be nice to fix this for people. |
Co-authored-by: rawataaryan9 <[email protected]>
Co-authored-by: rawataaryan9 <[email protected]>
Co-authored-by: rawataaryan9 <[email protected]>
Co-authored-by: rawataaryan9 <[email protected]>
The current iceberg table properties by design do not support any other value than non-null string values. However, due to a typo in the code, it allows a null value for a table property. Due to this we can store the value as null but breaks the read/load of iceberg table back due to non-null property values checks as part of metadata parsers.
This PR just updates the typo to ensure we cannot populate non-null values.
@rdblue @jackye1995 @aokolnychyi @RussellSpitzer