planner/cascades: introduce EngineType in physical property (experimental) #12437
Conversation
This file contains 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
Codecov Report
@@ Coverage Diff @@
## master #12437 +/- ##
===============================================
- Coverage 79.7567% 79.6387% -0.118%
===============================================
Files 462 461 -1
Lines 102034 101438 -596
===============================================
- Hits 81379 80784 -595
- Misses 14781 14832 +51
+ Partials 5874 5822 -52 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What problem does this PR solve?
In #12257, we tried to implement selection in cascades planner. But we found that introducing
EngineTypeinGrouptruly increases the complexity of the framework. So in this PR, I try to introduce EngineType in physical property.What is changed and how it works?
Check List
Tests
Code changes
Side effects