refactor: prefer usage of metadata and protocol fields #1935
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
roeap
requested review from
wjones127,
fvaleye,
ion-elgreco and
rtyler
as code owners
github-actions
bot
added
binding/python
roeap
changed the title
ion-elgreco
reviewed
Dec 3, 2023
ion-elgreco
approved these changes
Dec 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Another PR on our way to more kernel compatibility, less API surface, and arrow backed table state. Along also comes a minor update to our Add actions to include the recently added
clusteringProviderfield.Mainly we try to use
metadataandprotocoldirectly, rather then accessing individual fields via dedicated methods on our top levelDeltaTablestruct.Related Issue(s)
related: #1776