Alex, Evaluator.atDepth is really just a convenience method, you can always use the full Javascript notation for the return_filter, see http://docs.neo4j.org/chunked/snapshot/rest-api-traverse.html#rest-api-traversal-using-a-return-filterand thus do "position.length==3" for the query, since the position is a Path object, see http://components.neo4j.org/neo4j/1.5.M01/apidocs/org/neo4j/graphdb/Path.html.
Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Fri, Sep 2, 2011 at 4:42 PM, Alex <[email protected]> wrote: > Dear Neo4Jers > > is there anything like "at_depth" in the REST API? I only found > "max_depth", > although Evaluators.atDepth(depth) exists in the Java API. > > Cheers > Alex > > -- > View this message in context: > http://neo4j-community-discussions.438527.n3.nabble.com/REST-at-depth-tp3304387p3304387.html > Sent from the Neo4j Community Discussions mailing list archive at > Nabble.com. > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
