Use the gen4 planner for queries with outer joins #9671
Merged
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
systay
added
Backport
GuptaManan100
approved these changes
Feb 11, 2022
harshit-gangal
approved these changes
Feb 11, 2022
Signed-off-by: Andres Taylor <andres@planetscale.com>
systay
force-pushed
the
9657-backport-to-13
branch
from
08c4ddc
to
e1aa1af
Compare
|
@systay - Gotcha, thanks! |
frouioui
approved these changes
Feb 15, 2022
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.
Routing for queries that contain outer join was not being handled correctly.
It would require a lot of changes to support these queries correctly in V3, so instead this fix makes it so the gen4 planner is used in the presence of outer joins.
If you know that you want to use the v3 planner, that can still be accomplished by using the query hint
/*vt+ PLANNER=v3 */Related Issue(s)
Fixes #7700
Backport of #9657