Thanks Natal! Titan had a way to start with embedded Rexster which OrientDB do not. I need to write some Rexster extensions to run custom traversal and execution code. I now have following setup: 1) Rexster server running locally with OrientDB on same VM. Rexster server accesses orientdb locally(<graph-location>remote:127.0.0.1/test-graph</graph-location>) 2) Remote Rexster clients connect and execute gremlin rexster extension methods.
All Graph update is done using Orientdb Native client. Is this a correct approach? Negi On Sunday, March 29, 2015 at 6:27:06 PM UTC+5:30, Natal Kaplya wrote: > > You can access any orient(embedded,plocal or remote) from Java API. But > the URI inside graphfactory points on remote DB, when you're talking about > embedded. Not sure that understood you correct. > Rexster doesn't start Orient server, you have to do it manually, before > Rexster starts. > Rexster's gremlin performance is slower (in my tests with complex query - > 5x slower) than native Orient gremlin support(that in studio or Java API) > due to I\O overhead. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
