Date
1 - 5 of 5
JanusGraph 0.6.0 traversal change?
criminosis@...
When running with 0.5.2 I was able to do this traversal to add an edge between to vertices
But when doing it through 0.6.0 I get this now:
After fiddling with it though I noticed I was able to do this:
However just doing the vertex id is not permitted, which makes sense given it's just an integer with no context. I've been looking through the 0.6.0 milestone and found this issue, but that seemed more about a documentation change in 0.6.0 than a code change. Environment wise I'm just running these in a gremlin session within a docker-compose environment with Cassandra and Elasticsearch as backends. Just wondering if the change here is intentional? Seemed weird that it was suggesting to the use "__" class too. |
|
criminosis@...
Ahh I see, I guess this is the intended usage now?
Basically doing "__.V" instead of "g.V" for the child traversal? |
|
Clement de Groc
Yes. In JanusGraph 0.6.0, Apache TinkerPop was upgraded to 3.5.1 and requires using an anonymous traversal in such cases.
This is mentioned in their "Upgrade for users" guide here: https://tinkerpop.apache.org/docs/current/upgrade/#_anonymous_child_traversals |
|
Florian Hockmann
Yes, exactly. This was a breaking change in TinkerPop 3.5.0 which is included in JanusGraph 0.6.0: https://tinkerpop.apache.org/docs/current/upgrade/#_anonymous_child_traversals
Von: janusgraph-users@... <janusgraph-users@...> Im Auftrag von criminosis@...
Ahh I see, I guess this is the intended usage now?
Basically doing "__.V" instead of "g.V" for the child traversal? |
|
criminosis@...
Duly noted. I'll keep in mind to dig deeper when seeing closed issues mentioning Tinkerpop updates. Thanks everyone!
|
|