feat: add ProgressiveEval and rule to convert from SortPreservingMerge - #24546
Draft
adamreeve wants to merge 5 commits into
Draft
feat: add ProgressiveEval and rule to convert from SortPreservingMerge#24546adamreeve wants to merge 5 commits into
adamreeve wants to merge 5 commits into
Conversation
This was unused except for display purposes.
adamreeve
force-pushed
the
progressive-eval
branch
from
August 21, 2026 01:57
52c9757 to
0634301
Compare
|
Thank you for opening this pull request! Reviewer note: cargo-semver-checks reported the current version number is not SemVer-compatible with the changes in this pull request (compared against the base branch). Details |
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?
Related to #15191
Rationale for this change
Optimizes sorted reads by avoiding a merge when the inputs can simple be concatenated.
What changes are included in this PR?
ProgressiveEvalExecplan, based on feat: AddProgressiveEvaloperator #10490, but with some modifications.ReorderPartitionsExecplan, to allow reordering partitions when required to maintain a global order.SequenceSortedInputsoptimizer rule, that does the conversion fromSortPreservingMergeExectoProgressiveEvalExecwhen possible.Are these changes tested?
Yes, new tests have been added.
Are there any user-facing changes?
Yes. This adds to the public API and adds new configuration options, but the new optimization isn't enabled by default and there are no breaking changes.