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.

Sign up for GitHub

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

Jump to bottom

Limit query execution by work AKA hops query limit #1374

Open
4 of 5 tasks
gitbuda opened this issue Oct 17, 2023 · 2 comments · May be fixed by #1928
Open
4 of 5 tasks

Limit query execution by work AKA hops query limit #1374

gitbuda opened this issue Oct 17, 2023 · 2 comments · May be fixed by #1928
Assignees
@DavIvek
Labels
customer customer Effort - Very High Effort - Very High feature feature Frequency - EveryTime Frequency - EveryTime non-incremental Priority - Later Priority - Later Reach - Some Reach - Some Severity - S2 Severity - S2
Milestone
mg-v2.18.0

Comments

@gitbuda
Copy link
Member

gitbuda commented Oct 17, 2023 •
edited by DavIvek

USING HOPS LIMIT 100000 MATCH (n1)-[bfs*]->(n2) RETURN n2;

TODOs

  • Measure and expose hops back to the user (BFS+DFS+Expand; if an edge is filtered out, it should count as a hop)
  • Implement the syntax
  • Limit the execution
  • Add option to return partial results
  • OPTIONAL/NEXT/NOT_REQUIRED: Implement HOPS LIMIT under more advanced variable-expand options (wShortest, allShortest)
@gitbuda gitbuda added the feature feature label Oct 17, 2023
@as51340
Copy link
Contributor

as51340 commented Oct 19, 2023 •
edited

@gitbuda Do we talk here about absolute number of hops which would basically mean every possible expand we do or we talk about neigborhood, like 2-hop neighborhood?

@gitbuda
Copy link
Member Author

gitbuda commented Oct 20, 2023

@gitbuda Do we talk here about absolute number of hops which would basically mean every possible expand we do or we talk about neigborhood, like 2-hop neighborhood?

Every edge traversed because the traversal depth is already possible to limit under variable expand, e.g., bfs*..2 😃

@gitbuda gitbuda added Importance - I3 Importance - I3 Effort - High Effort - High Severity - S2 Severity - S2 labels Dec 6, 2023
@hal-eisen-MG hal-eisen-MG added Priority - Later Priority - Later and removed Priority - Later Priority - Later labels Feb 4, 2024
@hal-eisen-MG hal-eisen-MG added Priority - Later Priority - Later and removed Priority - Later Priority - Later labels Feb 18, 2024
@katarinasupe katarinasupe added Frequency - Monthly Frequency - Monthly Reach - VeryFew Reach - VeryFew customer customer Reach - Some Reach - Some and removed Importance - I3 Importance - I3 Reach - VeryFew Reach - VeryFew labels Feb 27, 2024
@Josipmrden Josipmrden added Frequency - EveryTime Frequency - EveryTime and removed Frequency - Monthly Frequency - Monthly Effort - High Effort - High labels Mar 26, 2024
@DavIvek DavIvek self-assigned this Apr 9, 2024
@DavIvek DavIvek linked a pull request Apr 10, 2024 that will close this issue
Open
7 tasks
@gitbuda gitbuda added this to the mg-v2.17.0 milestone Apr 11, 2024
@gitbuda gitbuda changed the title Limit query execution by graph space AKA hops query limit Limit query execution by work AKA hops query limit Apr 11, 2024
@gvolfing gvolfing added the Effort - Very High Effort - Very High label May 8, 2024
@gitbuda gitbuda modified the milestones: mg-v2.17.0, mg-v2.18.0 May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DavIvek DavIvek

Labels
customer customer Effort - Very High Effort - Very High feature feature Frequency - EveryTime Frequency - EveryTime non-incremental Priority - Later Priority - Later Reach - Some Reach - Some Severity - S2 Severity - S2
Projects
None yet
Milestone
mg-v2.18.0
Development

Successfully merging a pull request may close this issue.

Limit number of hops memgraph/memgraph
7 participants
@gitbuda @Josipmrden @as51340 @katarinasupe @DavIvek @gvolfing @hal-eisen-MG