OrientDB 1.7-rc1
February 6th 2014Changelog:

  • Engine: new LINKBag to manage LINKS by using SBTree indexes. This drastically improved performance
  • SQL: new LOCK keyword to specify locking strategy
  • SQL: new RETURNING keyword to let to UPDATE and DELETE commands to return modified records
  • SQL: new include() and exclude() to respectively include or exclude fields of documents
  • SQL: operator [] now can be used in chain, also with functions
  • SQL: projections can be reused as variables
  • SQL: support for LET also in UPDATE and DELETE commands
  • Graph API: support for ordered edge list
  • Graph API: new detach() and attach() method to work with Graph Element offline
  • Graph API: new OrientGraphFactory to manage pooled instances
  • HTTP: new support for ETag, If-Match and If-None-Match headers
  • HTTP: new PATCH method against /document command and /documentbyclass for partial updates
  • Distributed: database deploy now is chunked to avoid RAM saturation
  • Backup and Restore: improved speed from 5x to 50x
  • Studio: new CSV download of Query result
OrientDB 1.6.4
January 16th 2014Changelog:

  • Blueprints integrated in “graphdb” module
  • Hotfixes against 1.6.3
OrientDB 1.6.3UpgradeDecember 27th 2013Changelog:

  • Hotfixes against 1.6.2
OrientDB 1.6.2UpgradeDecember 9th 2013Changelog:

  • SBTree: new index engine with the support for transactions and range queries
  • Hotfixes against 1.6.1
OrientDB 1.6.1UpgradeNovember 20th 2013Hotfixes against 1.6. Look at the list of Changelog
OrientDB 1.6UpgradeOctober 31st 2013Changelog:

  • SBTree: new index engine with the support for transactions and range queries
  • Distributed: new Architecture based on Hazelcast, new Distributed Transaction support across
    nodes, new Database Sharding feature
  • Studio: total rewriting in a new tool hosted on separate project
  • HTTP: execute commands in batch mode, partial document updates, JSON as return of create and
    update documents, management of multi databases in the same connection
  • Scripts: new Orient variable to get database instances, new switchUser() API to change current
  • Plugins: new hot deployment plugin as folders, zip and jar files
  • SQL: new target “metadata” to retrieve schema and indexes
  • Console: new silent mode
  • Many features and performance improvements on plocal and hash indexes
OrientDB 1.5.1September 3rd 2013Hotfixes against 1.5.0. Look at the list of Changelog
OrientDB 1.5UpgradeJuly 29th 2013Changelog:

  • New PLOCAL (Paginated Local) storage engine. In comparison with LOCAL it’s more durable (no usage of MMAP) and supports better concurrency on parallel transactions. To migrate your database to PLOCAL follow this guide: migrate-from-local-storage-engine-to-plocal
  • New Hash Index type with better performance on lookups. It does not support ranges
  • New “transactional” SQL command to execute commands inside a transaction. This is useful for “create edge” SQL command to avoid the graph get corrupted
  • Import now migrates RIDs allowing to import databases in a different one from the original
  • “Breadth first” strategy added on traversing (Java and SQL APIs)
  • Server can limit maximum live connections (to prevent DOS)
  • Fetch plan support in SQL statements and in binary protocol for synchronous commands too
  • Bug fixing
OrientDB 1.4.1June 18th 2013Bug fixing. Changelog.
OrientDB 1.4June 7th 2013Changelog:

  • Graph: total rewrite of Blueprints API that now are the default Java interface, support for light-weight edges (no document), labeled relationships using separate classes and vertex fields
  • Storage: new Paged-Local compressed “plocal” engine (not yet transactional)
  • SQL: INSERT and UPDATE supports JSON syntax, improved usage of indexes upon ORDER BY, supported timeout in query and global, new create function command, flatten() now is expand(), new OSQLMethod classes to handle methods even in chain, new encode() and decode() functions, support for new dictionary: as target in SELECT and TRAVERSE
  • new SCHEDULER component using CRON syntax
  • new OTriggered class to use JS as hook
  • MMap: auto flush of pages on regular basis
  • Fetch-plan: support for skip field using “-2″
  • Index: auto rebuild in background, usage of different data-segment
  • Export: supported partial export like schema, few clusters, etc.
  • Console: improved formatting of resultsets
  • HTTP: new /batch command supporting transaction too, faster connection through /connect command, /document returns a JSON
  • Studio: UML display of class
OrientDB 1.3December 19th 2012Changelog:

  • SQL: new eval() function to execute expressions, new if(), ifnull() and coalesce() functions, supported server-side configuration for functions, new DELETE VERTEX and DELETE EDGE commands, execution of database functions from SQL commands, new create cluster command
  • Graph: bundled 2 algorithms: Dijkstra and ShortestPath between vertices
  • Performance: improved opening time when a connections is reused from pool, better management of indexes in ORDER BY
  • Schema: new API to handle custom fields
  • HTTP/REST: new support for fetch-plan and limit in “command”
  • Moved from Google Code to GitHub: https://github.com/orientechnologies/orientdb