fix SHORTEST queries #1388
Merged
fix SHORTEST queries #1388
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dogofbrian
requested changes
Sep 15, 2025
| ---- | ||
| The result is a significantly faster query (down from 59 to 9 milliseconds): | ||
| The result is a less resource intensive query: |
Contributor
There was a problem hiding this comment.
Is the drop in execution time not worth mentioning?
| This constraint will inform the planner of the uniqueness of `trail` values up front. | ||
| As a result, the simpler shortest path query (without a `CALL` subquery) will now generate a faster plan (using the `StatefulShortestPath(Into)`) operator with a cardinality of 1 for both the source and target nodes of the shortest path. | ||
| As a result, the simpler shortest path query (without a `CALL` subquery) will now generate a faster plan (using the `ShortestPath` operator) with a cardinality of 1 for both the source and target nodes of the shortest path. |
Contributor
There was a problem hiding this comment.
OK I didn't realise that both queries are planned as ShortestPath. So there is no example where SSP(Into) improves performance. I think we need that. The simplest thing to do would be to change the quantifier to {2,}.
Collaborator
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
JPryce-Aklundh
added a commit
that referenced
this pull request
Sep 17, 2025
JPryce-Aklundh
added a commit
that referenced
this pull request
Sep 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.