-
Notifications
You must be signed in to change notification settings - Fork 196
Added a fix for column rename in IcebergSchemaSync #712
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
base: main
Are you sure you want to change the base?
Added a fix for column rename in IcebergSchemaSync #712
Conversation
| verify(mockUpdateSchema).commit(); | ||
| } | ||
|
|
||
| @Test |
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.
Can we add a unit test which writes an actual iceberg table to a tempDir path? There are many examples in ITConversionController to follow from.
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.
I will take a look and will add it @vinishjail97
| // update the name of the column | ||
| if (!latestColumn.name().equals(currentColumn.name())) { | ||
| updates.put( | ||
| latestColumn.fieldId(), | ||
| () -> updateSchema.renameColumn(currentColumn.name(), latestColumn.name())); | ||
| } |
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.
I think column name should be done after updating the type?
The UT's are failing are probably because of 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.
I moved after updating the type and still it is failing. I will take a look
…nRenameInIcebergSchemaSync # Conflicts: # xtable-core/src/test/java/org/apache/xtable/iceberg/TestIcebergSchemaSync.java
FIxes #711