[k-hop]Remove useless inner join for go in simple case #4556
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
jievince
requested review from
nevermore3,
czpmango,
Shylock-Hg,
Aiee and
dutor
jievince
force-pushed
the
remove-useless-innerjoin
branch
from
5b383e4
to
f4d0b52
Compare
|
Where you create |
Aiee
reviewed
Aug 19, 2022
Comment on lines
+600
to
606
| if (goCtx_->isSimple) { | ||
| // We don't need to do a inner join in such case. | ||
| goCtx_->joinInput = false; | ||
| } | ||
| if (goCtx_->isSimple) { | ||
| goCtx_->yieldExpr->columns()[0]->setExpr(InputPropertyExpression::make(qctx->objPool(), kDst)); | ||
| } |
nevermore3
approved these changes
Aug 19, 2022
jievince
changed the title
Aiee
approved these changes
Aug 19, 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.
What type of PR is this?
What problem(s) does this PR solve?
Issue(s) number:
Description:
How do you solve it?
Special notes for your reviewer, ex. impact of this fix, design document, etc:
Checklist:
Tests:
Affects:
Release notes:
Please confirm whether to be reflected in release notes and how to describe: