Enable ObjectMeta Cache for ListingTable #10110
Closed
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
|
I think most of the time consumed should be in get_object, so maybe it is better to cache the parquet file |
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.
Which issue does this PR close?
Part of #9964
Closes #.
Rationale for this change
Currently the ListingTable on remote storage contains two parts, list_object, which is used to fetch the metadata, and get_object which is used to get the actual file,
we could cache the metadata for subsequent queries to use the metadata
What changes are included in this PR?
yes after adding cache, the following query has been faster for around 17%
Are these changes tested?
Are there any user-facing changes?