-
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
Inconsistent LIMIT operations #3151
Comments
lookup is based on the partition level and returned rows number is partition_num * limit . this is the original design. It's not a bug. |
I totally agree with it!The syntax of the inconsistency will make the user difficult to understand. |
I think that's a reasonable consideration. |
Nebula Graph version: 2021.10.18-nightly
LOOKUP ON player LIMIT 2
andLOOKUP ON player | LIMIT 2
return totally different numbers of rows.LIMIT
clause inLOOKUP
(without a pipe) is based on the partition level and the returned number of rows is not as specified in the LIMIT clause. This is inappropriate.It is recommended to optimize LIMIT so that its behaviors can be reasonable, logical, and consistent throughout nGQL (openCypher-compatible syntax included).
The text was updated successfully, but these errors were encountered: