Cypher (lack of) optimization on variable length path with WHERE NONE(...) #1961

Open
aseemk opened this Issue Feb 13, 2014 · 3 comments

Comments

Projects
None yet
4 participants

aseemk commented Feb 13, 2014

Not sure if you guys would consider this a bug or feature request =), but I was surprised to discover that a MATCH ... -[rels*]- ... + WHERE NONE(rel IN rels WHERE ...) query doesn't short-circuit the traversal the moment the first match fails. This is the only way I've been able to write a query to return the "first" matching relationship, as described here:

http://stackoverflow.com/questions/21746893/neo4j-cypher-find-first-matching-relationship-in-a-linked-list

Let me know if I can provide more info beyond that post. Thanks for the consideration!

Contributor

jakewins commented Dec 6, 2015

After two years of deep consideration, we have now decided this is a feature request ;)

Any update on this?

Member

jexp commented Feb 17, 2016

At least for shortest-path we pull in now predicates that are resolvable, @craigtaverner can tell you more. See: http://neo4j.com/docs/3.0.0-SNAPSHOT/query-shortestpath-planning.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment