-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow the expressions like 'v.tag' in return #5440
Conversation
770e36e
to
0dc2592
Compare
break; | ||
} | ||
auto tagId = ret.value(); | ||
propsUsed_.insertVertexProp(entityAlias, tagId, "*"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it necessary to insert edge and vertex props at same time? maybe only need to handle one branch by checking where the prop is from?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just found e.likeness
wouldn't reach here... Maybe this part was outdated. Let me check.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It goes into Kind::kSubscript
as $-.e[0]
. Maybe we can delete it already. 算了,不敢删。
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like we don't have sufficient information here to tell them apart. Any advise?
What type of PR is this?
What problem(s) does this PR solve?
Issue(s) number:
Fix #5329
Description:
'v.tag' means all properties of that tag are needed. They shall not be pruned by the optimizer.
How do you solve it?
Add a wildcard
"*"
into the VertexProp map in the tracker when encountered expressions likev.tag
after thetag
has been verified to be a real tag.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: