[fix](Nereids) fix a bug in multJoin: if there is no condition, create cross join#11772
Merged
924060929 merged 1 commit intoapache:masterfrom Aug 15, 2022
Merged
[fix](Nereids) fix a bug in multJoin: if there is no condition, create cross join#11772924060929 merged 1 commit intoapache:masterfrom
924060929 merged 1 commit intoapache:masterfrom
Conversation
Contributor
Author
|
@wangshuo128 @jackwener could you review, please |
Contributor
|
PR approved by anyone and no changes requested. |
morrySnow
approved these changes
Aug 15, 2022
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
4 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.
Proposed changes
In MultiJoin transform, if there is no condition, we should generate cross join instead of inner join
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...