Hi all, we're very close to merge the new storage structure to the 1.7 branch. Andrey has some *awesome numbers *about the performance of the new engine in terms of benchmarks, he will share them with us on this group very soon.
But in order to complete the merge, we should *remove the old Graph API: OGraphDatabase*! This is mainly for 2 big reasons: 1. it's not compatible with *Lightweight* edges and other improvements we introduced since version 1.4.x 2. it heavily uses *MVRB-Tree indexes* so it wouldn't scale on the new storage structure So after a while we deprecated the old Graph API, it's time to removed it from the v1.7 code base. I know some users are still sticked with this API, they can decide to: 1. Migrate to the Blueprints API (well documented on OrientDB & TinkerPop sites) 2. Stay with old API and remain sticked to last OrientDB v1.6.x. Obviously we strongly suggest 1st solution! For the users want to migrate we will provide a new guide to migrate the old code (very easy, most of the concepts are the same). In this way they could benefits of HUGE improvement with last version of OrientDB, specially with big databases. Any comments are welcome :-) Lvc@ -- --- 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/groups/opt_out.
