[CRITEO] Add the possibility to calculate partition stats after creat…#165
Merged
Merged
Conversation
ichraf7
force-pushed
the
auto-partition-stats
branch
from
November 5, 2025 10:11
9edb150 to
f613a57
Compare
…ing new partition
ichraf7
force-pushed
the
auto-partition-stats
branch
from
November 6, 2025 13:17
f613a57 to
c622d88
Compare
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.
Currently very basic stats are generated on table level when partition is created , we added feature (activated by default) that calculate stats at partition level when new partition is created, this avoid us from doing more complicated dev in BDF and less efficient with extra overhead.
What changes were proposed in this pull request?
Calculate partition stats when new partition is created
Why are the changes needed?
we need stats at partition level (like hive) to be able to activate spark optimizer which will have significant impact on performance, also presto//trino will use these stats to optimize its queries
Does this PR introduce any user-facing change?
'No'.
How was this patch tested?
local build , deploy and test in mozart