planner: allow TableDual to match the required property if the row count is 0 (#16927) #17014
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 #16927 to release-3.0
What problem does this PR solve?
Issue Number: close #16841
Problem Summary:
Before this PR, PhysicalTableDual cannot match any required property(and it will return an invalidTask in findBestTask if the property is not empty).
But the case in #16841 use a
MergeJoin
hint to enforce to use the merge join. While one child of the LogicalJoin is a LogicalTableDual, which cannot match the property. So the optimizer cannot find a physical plan for that SQL.What is changed and how it works?
What's Changed:
This PR allow TableDual to match the required property if the row count is 0.
How it Works:
Related changes
Check List
Tests
Release note