ArangoDB 2.7.2 comes with replication improvements and some bug fixes. You can download the latest version from our download page.

Replication improvements:

The upcoming 2.8 version of ArangoDB will provide several improvements in the area of index usage and query optimization.

First of all, hash and skiplist indexes can now index individual array values. A dedicated post on this will follow shortly. Second, the query optimizer can make use multiple indexes per collection for queries with OR-combined filter conditions. This again is a subject for another post. Third, there have been some speed improvements due to changes in the general index handling code. This is what this post is about.

In order to assess the speedups in 2.8, I have run some..

The implementation of the JavaScript require function will be adjusted to improve compatibility with npm modules. The current implementation in 2.7 and earlier versions of ArangoDB strictly adheres to the CommonJS module standard, which deviates from the behaviour implemented in Node and browser bundlers.

Module paths will now be resolved in the following ways:

• relative paths (e.g. ./hello) will be resolved relative to the current file
• absolute paths (e.g. /hello) will be resolved relative to the file system root
• global names (e.g. hello) will be resolved by looking in the following places:

The upcoming ArangoDB version 2.8 (currently in devel) will provide a much better deadlock detection mechanism than its predecessors.

The new deadlock detection mechanism will kick in automatically when it detects operations that are mutually waiting for each other. In case it finds such deadlock, it will abort one of the operations so that the others can continue and overall progress can be made.

In previous versions of ArangoDB, deadlocks could make operations wait forever, requiring the server to be stopped and restarted.

How deadlocks can occur

Here’s a simple example for getting into a..

In the first maintenance release of ArangoDB 2.7 we have switched from readline to linenoise ng for line-editing and history capabilities on the command line.

Furthermore, the AQL function MERGE() improved, now working on a single array parameter, too. This allows combining the attributes of multiple objects from an array into a single object, e.g.:

In ArangoDB 2.6.9 we have fixed an AQL skiplist issue that occurs in a combination of sort and limit.

We put a lot of brainpower into the next major release of our favorite database. Thanks to your feedback and contributions we got some important steps forward. Share your professional experiences, opinions and feedback with us on this release candidate of ArangoDB 2.7.

This is a quick info about the upcoming 2.7 release – for details please check our documentation and the changelog.

Performance

As performance and ease of use are part of our key goals, we worked hard on some major improvements. Thanks to your feedback and contributions we were able to implement some nice stuff like:

Index..

While preparing the release of ArangoDB 2.7, some improvements were made for the PHP driver for ArangoDB.

The 2.7 version of the PHP driver now supports the AQL query results cache. The cache can be turned on or off globally, or be set to demand mode. The demand mode will allow controlling caching on a per-AQL-query basis.

The release ArangoDB 2.6.8 fixes a memory access bug on ARM. So for your pet project on a Raspberry Pi you need to change the CPU alignment setting to allow unaligned memory access.

There is no need to update to 2.6.8 for other distributions.

A new maintenance release 2.6.7 is available for download.