feat: Prune ListingTable file groups for range-key filters - #25819
Open
goutamadwant wants to merge 1 commit into
Open
goutamadwant wants to merge 1 commit into
goutamadwant wants to merge 1 commit into
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #25819 +/- ##
========================================
Coverage 82.51% 82.52%
========================================
Files 1141 1142 +1
Lines 439801 439984 +183
Branches 439801 439984 +183
========================================
+ Hits 362916 363078 +162
- Misses 54943 54959 +16
- Partials 21942 21947 +5 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
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?
Rationale for this change
A
ListingTablescan with declared Range partitioning currently retains every file group even when a range-key filter proves that some groups cannot contain matching rows. For example,range_key < 10still planned all four groups for split points(10), (20), (30).What changes are included in this PR?
This does not yet compact partition counts or remove all downstream work for empty partitions.
What is the testing strategy for this PR?
range_key < 10and equality at the10split point retain only the expected file group; a join test verifies the resulting rows.cargo fmt --all --check,cargo clippy --all-targets --all-features -- -D warnings, focused tests, and the extended workspace test suite passed locally.Are there any user-facing changes?
Yes. Supported range-key filters can avoid reading file groups known not to match. There is no public API change.