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:
MATCH ... -[rels*]- ...
WHERE NONE(rel IN rels WHERE ...)
Let me know if I can provide more info beyond that post. Thanks for the consideration!
After two years of deep consideration, we have now decided this is a feature request ;)
Any update on this?
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