executor: fix wrong plan type for dataReaderBuilder... (#17028) #17036
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.
cherry-pick #17028 to release-4.0
What problem does this PR solve?
Issue Number: close #16973
Problem Summary:
After PR #16389 TiDB will push down all the expr supported by TiKV or TiFlash in predicate push down stage, so if there is an expr which only supported by TiFlash, a physical selection will be added after index read, but current implementation of
buildExecutorForIndexJoin
does not support physical selection, so it will throw wrong plan type for dataReaderBuilder error when meeting physical selection plan.What is changed and how it works?
What's Changed:
support physical selection in
buildExecutorForIndexJoin
Related changes
Check List
Tests
Release note