Improve over-estimating for ORC coalescing reading #3275
Merged
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.
This PR is for issue #2945 .
Let's assume we're coalescing 2 orc files with 2 stripes for each file in a Spark Task.
The original initial estimated size like below,
We have added all ORC file's FOOTER size (size_of FOOTER1 + size_of FOOTER2) in order to estimate the StripeInformation size in FOOTER. It seems a little over-estimating since FOOTER size includes not only StripeInformation but also Schema/ColumnStatistics ...
This PR uses a fixed worst-case StripeInformation size instead of using ORC files' FOOTER size.
Below is the comparing test on 5000 orc files total 1.3G
Please be note, we have added
128 * 1024
as the fudging. If we reduce this size, the over-estimating can only be1.6M - 12 * (128*1024) = 102K
and20.6M - 162 * (128*1024) = 358.4K