feat(cubesql): Push Limit-Sort down Projection #9776
Merged
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.
Check List
Description of Changes Made
This PR adds Limit-Sort to Projection push down rule which helps queries that could be planned as CubeScan but contain complex Projections that cannot be pushed down, and as such get planned using SQL push down.
It also fixes an issue with Limit-Sort combinations not being prioritized lower than SQL push down when Limit-Sort is not at the top of the plan.
Related test is included.