Predicates on shortest path and optional match#9156
Merged
craigtaverner merged 1 commit intoneo4j:3.1from Apr 6, 2017
Merged
Conversation
When combining `OPTIONAL MATCH` and `shortestPath` with predicates we forgot to keep track of the relationship name of the shortest path pattern, causing the cost planner to choke on such queries.
craigtaverner
approved these changes
Apr 6, 2017
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
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.
When combining
OPTIONAL MATCHandshortestPathwith predicates weforgot to keep track of the relationship name of the shortest path pattern,
causing the cost planner to fail on such queries.