-
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
add optimizer comments #3910
add optimizer comments #3910
Conversation
* 1. reduce the copy of memory between nodes | ||
* 2. reduces expression overhead in some cases(similar to column pruning) | ||
*/ | ||
/* |
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 believe we should use //
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.
Any reference?
Google style?
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.
Google style doesn't declare that the comments should use //
, but it suggests that the comments style should be unified. I think it makes sense. And the most open source projects i had ever seen use the //
. For now i have seen much styles in our project, it's too ugly.
//
/*
*/
/**
*
*/
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.
ACK.
6cb22de
to
3b13e8b
Compare
b642e5e
to
3f47693
Compare
bool changed_{true}; | ||
graph::QueryContext *qctx_{nullptr}; | ||
// Memo memory management in the Optimizer phase |
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.
What is memo?
// +--------+--------+ | ||
// | Limit | | ||
// | (limit=3) | | ||
// +--------+--------+ | ||
// | | ||
// +---------+---------+ | ||
// | AppendVertices | | ||
// +---------+---------+ | ||
// | | ||
// +---------+---------+ | ||
// | ScanVertices | | ||
// | (limit=3) | | ||
// +---------+---------+ |
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.
Will there still be a limit node after optimization?
bool changed_{true}; | ||
graph::QueryContext *qctx_{nullptr}; | ||
// Memo memory management in the Optimizer phase |
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.
What's this?
What type of PR is this?
Checklist:
Tests:
Affects:
Release notes: