Skip to content
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

Optimization on MATCH LIMIT #2653

Open
wey-gu opened this issue Jun 9, 2021 · 1 comment
Open

Optimization on MATCH LIMIT #2653

wey-gu opened this issue Jun 9, 2021 · 1 comment
Labels
type/enhancement Type: make the code neat or more efficient

Comments

@wey-gu
Copy link
Contributor

wey-gu commented Jun 9, 2021

Is your feature request related to a problem? Please describe.
There is no limit push down for MATCH, for a query like match (v: people) return v limit 5; cannot be done in an accepted performance

Describe the solution you'd like
Support push down of limit in this query pattern.

Describe alternatives you've considered
n/a

Additional context

@wey-gu
Copy link
Contributor Author

wey-gu commented Jun 17, 2021

Update:
Not sure if this case(limit in a string matching MATCH condition) could be covered in this optimization attempt, I put it here all together :-)

MATCH (v:vertexCall) WHERE v.CallNumber STARTS WITH "10000106" RETURN v.CallNumber as number | limit 2

@CPWstatic CPWstatic transferred this issue from vesoft-inc/nebula-graph Aug 27, 2021
@CPWstatic CPWstatic added the type/enhancement Type: make the code neat or more efficient label Aug 27, 2021
yixinglu pushed a commit to yixinglu/nebula that referenced this issue Sep 14, 2023
small fix fmt

small fix

Co-authored-by: Sophie <84560950+Sophie-Xie@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement Type: make the code neat or more efficient
Projects
None yet
Development

No branches or pull requests

3 participants