Track applicable optimizer rules#19902
Merged
mlyublena merged 1 commit intoprestodb:masterfrom Jun 20, 2023
Merged
Conversation
pranjalssh
approved these changes
Jun 16, 2023
Contributor
pranjalssh
left a comment
pranjalssh
left a comment
There was a problem hiding this comment.
Please squash the commits before merging. Accepting as I'll be offline for a while.
mlyublena
force-pushed
the
track-applicable-optimizer-rules-2
branch
from
2bad1a1 to
2d55c43
Compare
Contributor
Author
done. Had it as two commits initially to show the deleted file |
28 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The original commit for tracking applicable optimizers was reverted had a file with rebase markers checked in by mistake. This PR resubmits the original commit 5039ce5 without the redundant file (PushAggregationThroughOuterJoin.java.orig)