ESQL: mv_expand pushes down a limit copy and keeps the limit after it untouched (#100782) #101268
Conversation
This file contains 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
… untouched (elastic#100782) - allow mv_expand to push down limit and project past it - accept a limit after mv_expand when there is also a second limit before the mv_expand - adds a default TopN for cases when there is only a sort at Lucene level - adds OrderBy node type to the exceptions for duplicating the limit after mv_expand (cherry picked from commit 4679b09)
astefan
added
>bug
backport
auto-merge-without-approval
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.
ESQL: mv_expand pushes down a limit copy and keeps the limit after it untouched (#100782)
(cherry picked from commit 4679b09)