Use list length bounds for zone pruning - #8924
Draft
mhk197 wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Matt Katz <mhkatz97@gmail.com>
Merging this PR will improve performance by 13.25%
Performance Changes
Tip Curious why this is faster? Comment Comparing Footnotes
|
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.
Stacked on
Rationale for this change
List-length bounds can prune list_length predicates at the zone level without evaluating list sizes. Keeping this integration separate lets the underlying aggregate land and evolve independently from zoned storage and predicate rewriting.
What changes are included in this PR?
Validation