-
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
support properties expression in WHERE clause for LOOKUP #4848
Comments
The same as FETCH, It's necessary to make it(syntax) align. struct LookupContext final : public AstContext {
bool isEdge{false};
bool dedup{false};
bool isEmptyResultSet{false};
int32_t schemaId{-1};
Expression* filter{nullptr}; // using ExpressionProps repleace it?
YieldColumns* yieldExpr{nullptr};
std::vector<std::string> idxReturnCols;
std::vector<std::string> idxColNames;
// order by
}; |
BTW @BOFA1ex , are you planning open-sourcing your downstream OGM ;) |
Exactly, the OGM framework is bound to our internal-biz product. But i'm glad to make it nebula-contrib better together :) |
Thanks~~ And whenever you are considering splitting the OGM part and open-sourcing, let us know! |
It will consider compatible with 2.6.x~3.x? : upstream |
It seems that it has become inactive, any planning as feature on next milestone? |
Introduction
By intuition, this is reasonable and we could infer that it's equivalent to
player.mane == "Tony Parker"
, also, it's supported in GO to doWHERE properties($$) == "foo"
.Plus, those who are building ORM/templating dev job will benefit from this, too.
Contents
https://discuss.nebula-graph.com.cn/t/topic/11126/12
Related work
The text was updated successfully, but these errors were encountered: