London, November 18, 2014
Orient Technologies released OrientDB 2.0-M3. This is last Milestone before the 2.0-final. We fixed many issues reported in M2 and we supported some new features we are sure you’ll appreciate: 115 issues in total. Please help us to test OrientDB 2.0-M3 so that we can release a stable final 2.0 in few days.
- Core: - Cluster selection strategy now can decide on the input document content - Better automatic alloc of Heap and Disk-Cache - Clusters can be detached (offline) and re-attached (online) - FetchPlan: support for wildcards - Improved pools - Using SIGTRAP (kill -5) to dump OrientDB information - Fixed connection pool problem on high usage - Cache is always ON and can’t be disabled anymore. This avoids many common issues with users - Schema: used immutable instances to reduce locking contention - Graph API: - New OGraphBatchInsertBasic and OGraphBatchInsert API for massive insertion on graphs: - 13x faster than Blueprints - Document API: Removed a couple of internal layers to speedup and simplify implementation - Studio: Simplified database creation (graph - no lightweight edges by default) - Console: Displayed also @class - Bug fixing: 115 total issues from 2.0-M2.
No. This is not the final 2.0 version. This release is the third milestone (M3 stands for Third Milestone) of 2.0 on the path to the final version in the next days. We suggest using OrientDB v2.0-M3 in development and test only. If you plan to go in production before December, we suggest staying with OrientDB 1.7.x. Otherwise, go ahead and use OrientDB 2.0-M3.
You can open any database created with past versions of OrientDB. In order to use the new binary serialization, you are required to export and re-import the database. For more information, take a look at Migrate from 1.7.x.
Have fun with graphs & documents,
CEO of Orient Technologies
the Company behind OrientDB