-
Notifications
You must be signed in to change notification settings - Fork 2.5k
[CALCITE-7680] PruneEmptyRules should prune Sort when OFFSET is greater than or equal to max input rows #5132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
xuzifu666
wants to merge
6
commits into
apache:main
Choose a base branch
from
xuzifu666:sort_offset_fix
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 4 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
94698b9
[CALCITE-7680] PruneEmptyRules should prune Sort when OFFSET is great…
xuzifu666 659ee7a
Addressed
xuzifu666 a4276c8
Addressed
xuzifu666 4dd4d6c
Addressed
xuzifu666 16d480b
Addressed
xuzifu666 6d0064e
Addressed
xuzifu666 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is an improvement, but I still don't understand why this cannot be applied to any Rel node.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right that
isRelDefinitelyEmptyitself is generic.The reason this rule is specific to Sort is that the replacement logic is not generic:
RemoveEmptySingleRulecan safely turn anySingleRelinto an empty Values, but Join, Union, Intersect, Minus, and Aggregate each need their own logic when they are empty. This rule reuses RemoveEmptySingleRule because Sort is a SingleRel. A fully generic prune anything that is definitely empty rule would need a way to know how to rewrite each operator type correctly. The existing EMPTY_TABLE_INSTANCE follows the same pattern: it uses isRelDefinitelyEmpty but only for TableScan.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What matters is that the operator has a single OUTPUT, and they all do.
Maybe you can find a way to do it, even if it means writing a bit more code to handle operators with more than 1 input.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, I generalized ZeroMaxRowsRuleConfig (EMPTY_TABLE_INSTANCE) to match any RelNode that is definitely empty, not just TableScan. It excludes Values and TableModify (the latter may have side effects). This removes the need for a separate Sort-specific rule, so SORT_EMPTY_INSTANCE was deleted and SORT_FETCH_ZERO_INSTANCE is now a deprecated alias. The rule still relies on RelMdUtil.isRelDefinitelyEmpty, so the logic remains simple and covers LIMIT 0, large OFFSET, and any other case where Sort's max row count is zero.