Hi Christofer, Lightweight edges are a fundamental component in OrientDB Graph API. We decided to disable it by default when you create new databases, because most of the users have problem to get it working properly. So we decided to put the "lightweight edges" as a feature to use at tuning time.
Lvc@ On 22 January 2015 at 13:13, Christopher Roscoe < [email protected]> wrote: > In OrientDB 2.0 release lightweight edges are disabled by default. > https://github.com/orientechnologies/orientdb/wiki/Lightweight-Edges > > This breaks some of our application code, e.g. > com.orientechnologies.orient.core.command.traverse.OTraverse results now > containing edges. > getGraph().getVertex(vertex).traverse().field("out_" + edgeName).execute(); > > This call used to give back vertices. > Now it also contains edges, that we would have to filter out. > > As a quick fix we restored the old behaviour by setting the value > OrientConfigurableGraph#setUseLightweightEdges(true). > > Two questions: > > 1. How would you migrate such OTraverse code to give back the old behavior? > > 2. Now with lightweight edges disabled by default, will the option to > enable it (OrientConfigurableGraph#setUseLightweightEdges(true)) stay in > the long-run? > Or are there plans to drop the support for lightweight edges? > > -- > > --- > 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. > -- --- 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.
