Hi, mvrbtree was created for local storage and uses cache based on Java heap, so all operations with heap is out of control of WAL (they are not recorded). That is reason of incompatibility.
New data structure is disk cache based (uses direct memory), so no OOM (disk will be used in such case) no GC overhead, and all operations are logged. Other question, the version 1.7 can use directly a DB created by the 1.6.x ? Not graph database, we will provide migration tool next week, possible option is export/import to/from GraphML format. On Wed, Feb 5, 2014 at 8:05 PM, Laurent Quérel <[email protected]>wrote: > Other question, the version 1.7 can use directly a DB created by the 1.6.x > ? > > -- > > --- > 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. > -- Best regards, Andrey Lomakin. Orient Technologies the Company behind OrientDB -- --- 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.
