planner: fix dropping non-ScalarFunction when extractCol for memtable (#40935) #51186
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.
This is an automated cherry-pick of #40935
Signed-off-by: Zhenchi zhongzc_arch@outlook.com
Issue Number: close #40937
Problem Summary:
We can see
extractLikePatternCol
andextractTimeRange
will keep non-ScalarFunctions by appending them to remained.tidb/planner/core/memtable_predicate_extractor.go
Lines 432 to 437 in d6302c1
tidb/planner/core/memtable_predicate_extractor.go
Lines 265 to 270 in d6302c1
But not for
extractCol
. It seems a bug.tidb/planner/core/memtable_predicate_extractor.go
Lines 210 to 214 in d6302c1
What is changed and how it works?
Keep them the same.
Before this patch:
With this patch:
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.