Compute best mv in PruneCandidates optimizer
#73
Closed
Conversation
This file contains hidden or 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
xudong963
commented
Jul 9, 2025
|
|
||
| fn properties(&self) -> &PlanProperties { | ||
| self.candidates[self.best].properties() | ||
| self.candidates[0].properties() |
Member
Author
There was a problem hiding this comment.
I believe there will be potential bug, need to think more 🤔
Member
Author
There was a problem hiding this comment.
I added some NOTES for the method to avoid potential bug
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.
Before the PR, the best mv will be computed at the initialization of
OneofExec, before the physical optimizer, it doesn’t make sense, because filter pushdown in DF48 is in a physical optimizer rule.