-
Notifications
You must be signed in to change notification settings - Fork 3k
Core: Remove TableOperations from metadata tables. #6357
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: Remove TableOperations from metadata tables. #6357
Conversation
b8fbba7 to
f9ed0d0
Compare
szehon-ho
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.
Looks good to me. I guess it also as a consequence removes TableOperations from the BaseTableScan hierarchy, but seems to me a good simplification if we never needed it there.
| @Override | ||
| public FileIO io() { | ||
| return operations().io(); | ||
| return ops.io(); |
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.
These are unrelated , and just simplification/standardization, right? Fine with me either way
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.
Where possible, I removed references to methods that expose TableOperations and deprecated the methods.
Here in BaseTable, I just wanted to be more consistent and use the instance field directly.
|
@rdblue looks like this needs some RevAPI changes because the APIs changed |
f9ed0d0 to
de03fc7
Compare
|
Thanks for the review, @szehon-ho! |
This removes the use of
TableOperationsfrom metadata tables. WhereTableMetadatais needed, operations is fetched from theTableinstance instead of passing the ops explicitly. This is in preparation for metadata tables that are not tied to a particular Iceberg table.