HIVE-29416: optimise extrapolation by fetching matched partition col rows with one query#6602
Open
cyanzheng2926 wants to merge 1 commit into
Open
Conversation
…xtrapolation Replace db query for min/max extrapolation in each run with one fetch. Scan all partition rows retrieved to find min/max borders for partially collected partition column stats. Added unit tests
cyanzheng2926
force-pushed
the
HIVE-29416_optimise_extrapolation
branch
from
2505402 to
9254635
Compare
asf-ci-hive
added
tests failed
tests pending
and removed
tests pending
tests failed
labels
|
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
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.
What changes were proposed in this pull request?
Replace per min/max col query used for min/max extrapolation in
DirectSqlAggrStats.aggrStatsUseDBwith a single query that fetchesPART_NAMEand all relevant min/max stat columns. Scan all returned partition rows to find the global min/max borders before linear extrapolation.Why are the changes needed?
When aggregating column stats over partitions with partial stats, min/max values need to be extrapolated from partitions with stats. Previous implementation runs the same query to db per min/max column required for extrapolation, same query is executed multiple times in this case.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Added unit tests under
TestObjectStore.javafor extrapolation with partial partition stats