[core] Fix parquet performance regression in reader init #6802
Conversation
This file contains hidden or 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
mxdzs0612
force-pushed
the
gh/parquet-builder
branch
from
898da2a to
4e966bb
Compare
mxdzs0612
force-pushed
the
gh/parquet-builder
branch
from
4e966bb to
667a822
Compare
Contributor
|
Thanks @mxdzs0612 for the contribution. Like my previous experience, upgrading does come at a cost = = ... |
Contributor
|
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Purpose
Fix a query performance regression problem we found in trino when upgrading paimon-bundle from lower version. The flame graph is listed below.
trino_profile.html
This PR is the same as what Iceberg did in apache/iceberg#12305
Tests
already covered
API and Format
no
Documentation
no