Hi,
Thank you!
Thought that it could not be easy :-) Meantime realized that there are nodes and egdes in chain :-) but not projected result sets like in rdbms world.
Unfortunately I am not a developer, but a guy in business side with some it skill, so somehow I need to make it with out of the box solution to proof that it worth to spend time on it. So maybe javascript function can be the answer somehow.
@Andrey, could you please share your use case and solution with me? Orientdb lacks of complete, step by step tutorial, or at least I did not find too many.
Thx!
L.
--
---
You received this message because you are subscribed to a topic in the Google Groups "OrientDB" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/orient-database/IKbefI2QA3M/unsubscribe.
To unsubscribe from this group and all its topics, send an email to orient-databa...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
g.v('#21:7').as('person').both('RELATED').loop('person'){it.object.id.toString() != '#16:10' && it.loops < 4}.filter{it.id.toString()=='#16:10'}.path()
OrientGraph graph = DatabaseManager.getInstance().getDatabase("remote:192.168.200.128/ePersona").getConnection();
Pipe pipe = Gremlin.compile("_().as('person').both('RELATED').loop('person'){it.object.id.toString() != '#16:10' && it.loops < 4}.filter{it.id.toString()=='#16:10'}.path()[10..20]");
pipe.setStarts(new SingleIterator<Vertex>(graph.getVertex("#21:7")));
Merger m = new Merger();
Path paths = m.mergePathsResults(pipe);
for(Object o : pipe) {
ArrayList<Vertex> path = (ArrayList<Vertex>)o;
for(Vertex v:path){
System.out.print("->" + v.getProperty("name") + "[" + v.getProperty("@class") + "]");
}
System.out.println();
}
Hi Andrew'
It's something useful to play with :-)
Meantime I have started to get it work in javascript function.
May I know if you have faced to performance problems? My friends told me that it was not easy to sort it out with gremlin on a bitcoin database. How much data you deal with?
I have approx:
- vA: 1 million
- vB: 2 million
- vC: around 200-300 million
- vD: 2 million
- vE: 200 k
And having few other class of vertices, 1 million each.
I think it still not "big data", but something I can manage on a commodity oracle server. But it is not good for realtime recommender engine, although the performance is pretty good :-)
Thx!
L.