-
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
function on field names does not work when the nGQL starts with 'LOOKUP' #5341
Comments
what's your nebulagraph core version? |
For the lookup query, it's a typical tabular query(or, not a graphy one), that is, when we are query data with LOOKUP, it's a duplicated data on given tag/edgetype stored in a tabular way(like RDBMS), and NebulaGraph is not designed for such purposes. Thus, the expression like While in GO case, the filter expression can be done as it's just filtering on top of one graph traversal fetched data, thus in such volume of data(one hop graph traversal v.s. full scan of tag:comment), it's allowed and acceptable. Actually, the GO case with |
This is not a bug, as explained by @wey-gu. Close this issue for now. If you want more functions from LOOKUP, please issue some feature requests. Thanks. |
Cluster Config
metad: 3
graphd: 6
storaged: 6
Space Config
VID: FIXED_STRING(30)
Replica factor: 1
Partition Num: 30
Problem
When the nGQL starts with 'LOOKUP' and threre are some functions on field names after WHERE condition, such as:
the error occurs:
However, when I modify the nGQL with 'GO', such as:
the nGQL works well, it seems that there are differences on function process between 'GO' and 'LOOKUP'
The text was updated successfully, but these errors were encountered: