[UT][BugFix] fix PullUpScanPredicateRule (backport #53740) #53837
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.
Why I'm doing:
What I'm doing:
Fixes https://github.com/StarRocks/StarRocksTest/issues/8896
Fix some bugs in
PullUpScanPredicateRule
:when there is a limit on ScanOperator, we need to extract the limit from ScanOperator to FilterOperator
for this problem, we cannot directly give up extracting related expressions from scan predicates, otherwise we will lose many opportunities to reuse expressions.
my solution: after extracting the reserved predicate in FilterOperator, we also need to collect the expressions that can be used for subfield column pruning, then add them to the scan projection and replace them with column ref in the final predicate.
taking this query as an example, before fixing, we need read the whole json column since json columns are in project node.
after fixing, only json_query(xx) in project node, we don't need read the whole column
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist: