Hi, Currently, as I understand it, there is no way to traverse only a part of those edges looking for a range of edge/vertex values. I think edge indexing is on the 2.1 roadmap which will makes this more feasible.
Regards, -Stefan On Monday, 12 January 2015 10:21:18 UTC, Andrei Stoiculescu wrote: > > Hello, > > I have the following use case : > > I want to model a UserSession onto a website, and I am thinking to keep > the IP address node as a separate node. > So each time a User with the given IP x would connect to the website, a > UserSession pointing to the IP x would be created. > Over time, the IP address node would have probably hundreds of millions of > incoming edges, or more if more users have the same IP. > > What are the bottlenecks of this approach? > > Thanks and Regards, > Andrei > -- --- 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.
