[Neo4j] Traversals in REST Service vs. Traversals in neo4j.py
I'm developing the support to traversals for Python REST Client. The underlying idea for me is to mantain the compatibility with neo4j.py (a really hard issue), but the traversals made me to think about some questions: 1. How can I implement support to isStopNode or isReturnable in REST Service? I guess that for isStopNode I may to use prune evaluator, but what about with isReturnable, must I use returnable filer? Why this parameter has no body attribute in order to define a function? 2. If max depth parameter is not set, it's equivalent to STOP_AT_END_OF_GRAPH? If that's not true, how can I get the a behaviour like STOP_AT_END_OF_GRAPH? Sorry, perhaps they are dumb questions, but I need some of light, please. Best regards. -- Javier de la Rosa ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Traversals in REST Service vs. Traversals in neo4j.py
2010/6/2 Javier de la Rosa ver...@gmail.com:
I'm developing the support to traversals for Python REST Client. The
underlying idea for me is to mantain the compatibility with neo4j.py (a
really hard issue), but the traversals made me to think about some
questions:
1. How can I implement support to isStopNode or isReturnable in REST
Service? I guess that for isStopNode I may to use prune evaluator, but
what about with isReturnable, must I use returnable filer? Why this
parameter has no body attribute in order to define a function?
You can specify return filter just as you can do prune evaluator, like:
...
return filter: {
language: javascript,
body: position.node().getProperty( 'name' ).equals( 'Javier' )
}
...
2. If max depth parameter is not set, it's equivalent to
STOP_AT_END_OF_GRAPH? If that's not true, how can I get the a behaviour like
STOP_AT_END_OF_GRAPH?
If max depth isn't supplied max depth 1 is assumed. To get the
STOP_AT_END_OF_GRAPH behaviour you should do:
...
prune evaluator: {
language: builtin,
value: none
}
which converts into PruneEvaluator.NONE.
Sorry, perhaps they are dumb questions, but I need some of light, please.
Not at all, I hope this helps you!
Best regards.
--
Javier de la Rosa
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
--
Mattias Persson, [matt...@neotechnology.com]
Hacker, Neo Technology
www.neotechnology.com
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Traversals in REST Service vs. Traversals in neo4j.py
Thank you for your clarification.
On 2 June 2010 13:31, Mattias Persson matt...@neotechnology.com wrote:
return filter: {
language: javascript,
body: position.node().getProperty( 'name' ).equals( 'Javier' )
}
Will we see language: python in the near future?
--
Javier de la Rosa
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Traversals in REST Service vs. Traversals in neo4j.py
And one more question, what's the meaning of uniqueness: node path parameter? What values does it support? Which is the equivalent en neo4j.py? -- Javier de la Rosa ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Traversals in REST Service vs. Traversals in neo4j.py
I don't think the python bindings (or any other binding) has caught up to the new traversal framework. Uniqueness is all about when to visit a node and when not to. If the uniqueness would be NODE_GLOBAL a node wouldn't be visited more than once in a traversal. NODE_PATH means that a node won't be visited again for the current path (the path from the start node to where ever the traverser is at the moment) if that node is in the current path. It might as well be visited again in another path. Also see the javadoc of Uniqueness at http://components.neo4j.org/neo4j-kernel/apidocs/org/neo4j/graphdb/traversal/Uniqueness.html 2010/6/2 Javier de la Rosa ver...@gmail.com: And one more question, what's the meaning of uniqueness: node path parameter? What values does it support? Which is the equivalent en neo4j.py? -- Javier de la Rosa ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user -- Mattias Persson, [matt...@neotechnology.com] Hacker, Neo Technology www.neotechnology.com ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Traversals in REST Service vs. Traversals in neo4j.py
2010/6/2 Javier de la Rosa ver...@gmail.com:
Thank you for your clarification.
On 2 June 2010 13:31, Mattias Persson matt...@neotechnology.com wrote:
return filter: {
language: javascript,
body: position.node().getProperty( 'name' ).equals( 'Javier' )
}
Will we see language: python in the near future?
Yep, I very much hope so!
--
Javier de la Rosa
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
--
Mattias Persson, [matt...@neotechnology.com]
Hacker, Neo Technology
www.neotechnology.com
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Traversals in REST Service vs. Traversals in neo4j.py
On 2 June 2010 16:21, Mattias Persson matt...@neotechnology.com wrote: I don't think the python bindings (or any other binding) has caught up to the new traversal framework. Uniqueness is all about when to visit a node and when not to. If the uniqueness would be NODE_GLOBAL a node wouldn't be visited more than once in a traversal. NODE_PATH means that a node won't be visited again for the current path (the path from the start node to where ever the traverser is at the moment) if that node is in the current path. It might as well be visited again in another path. Also see the javadoc of Uniqueness at http://components.neo4j.org/neo4j-kernel/apidocs/org/neo4j/graphdb/traversal/Uniqueness.html Great! Thank you so much. -- Javier de la Rosa ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
