This version is deprecated. Download the new version of ArangoDB

A maintenance release for ArangoDB 2.2 is available from the usual channels. v2.2.3 (2014-09-02) ——————-
* added `around` for Foxx controller
* added `type` option for HTTP API `GET /_api/document?collection=…` This allows controlling the type of results to be returned. By default, paths to documents will be returned, e.g.

[
        `/_api/document/test/mykey1`,
        `/_api/document/test/mykey2`,
        ...
      ]

To return a list of document ids instead of paths, the `type` URL parameter can be set to `id`:

    <pre>[
    `test/mykey1`,
    `test/mykey2`,
    ...
  ]

To return a list of document keys only, the `type` URL parameter can be set to `key`:

    <pre>[
    `mykey1`,
    `mykey2`,
    ...
  ]

*   properly capitalize HTTP response header field names in case the \`x-arango-async\` HTTP header was used in a request.
*   fixed several documentation issues
*   speedup for several general-graph functions, AQL functions starting with \`GRAPH_\` and traversals</ul>

This version is deprecated. Download the new version of ArangoDB

A maintenance release of ArangoDB 2.2 is available via the package manager or from our download page.

v2.2.2 (2014-08-08)

• allow storing non-reserved attribute names starting with an underscore Previous versions of ArangoDB parsed away all attribute names that started with an underscore (e.g. `_test`, `_foo`, `_bar`) on all levels of a document (root level and sub-attribute levels). While this behavior was documented, it was unintuitive and prevented storing documents inside other documents, e.g.:

{
        "_key" : "foo",
        "_type" : "mydoc",
        "references" : [
          {
            "_key" : "something",
            "_rev" : "...",
            "value" : 1
          },
          { 
            "_key" : "something else",
            "_rev" : "...",
            "value" : 2
          }
        ]
      }

In the above example, previous versions of ArangoDB removed all attributes and sub-attributes that started with underscores, meaning the embedded documents would lose some of their attributes. 2.2.2 should preserve such attributes, and will also allow storing user-defined attribute names on the top-level even if they start with underscores (such as `_type` in the above example).

• fix conversion of JavaScript String, Number and Boolean objects to JSON. Objects created in JavaScript using `new Number(…)`, `new String(…)`, or `new Boolean(…)` were not converted to JSON correctly.
• fixed a race condition on task registration (i.e. `require(“org/arangodb/tasks”).register()`) this race condition led to undefined behavior when a just-created task with no offset and no period was instantly executed and deleted by the task scheduler, before the `register` function returned to the caller.
• changed run-tests.sh to execute all suitable tests.
• switch to new version of gyp
• fixed upgrade button

This version is deprecated. Download the new version of ArangoDB

A maintenance release for ArangoDB 2.2 is available. It will fix the performance problems encountered with the new graph module plus

v2.2.1 (2014-07-24)

• fixed issue with –check-version: when creating a new database the check failed
• issue #947 Foxx applicationContext missing some properties
• added startup option `–wal.suppress-shape-information` Setting this option to `true` will reduce memory and disk space usage and require less CPU time when modifying documents or edges. It should therefore be turned on for standalone ArangoDB servers. However, for servers that are used as replication masters, setting this option to `true` will effectively disable the usage of the write-ahead log for replication, so it should be set to `false` for any replication master servers. The default value for this option is `false`.
• added optional `ttl` attribute to specify result cursor expiration for HTTP API method `POST /_api/cursor` The `ttl` attribute can be used to prevent cursor results from timing out too early.
• (reported by Christian Neubauer): The problem was that in Google’s V8, signed and unsigned chars are not always declared cleanly. so we need to force v8 to compile with forced signed chars which is done by the Flag: -fsigned-char at least it is enough to follow the instructions of compiling arango on rasperry and add “CFLAGS=’-fsigned-char'” to the make command of V8 and remove the armv7=0
• Fixed a bug with the replication client. In the case of single document transactions the collection was not write locked.

This version is deprecated. Download the new version of ArangoDB

Well, it is “release week”. If you have not yet switch to ArangoDB 2.x, we have a released a maintenance release for ArangoDB 1.4:

v1.4.16 (2014-05-29)

• fixed too eager datafile deletion this issue could have caused a crash when the compaction had marked datafiles as obsolete and they were removed while “old” temporary query results still pointed to the old datafile positions
• fixed issue #826: Replication fails when a collection’s configuration changes

This version is deprecated. Download the new version of ArangoDB

For those of you, you have not yet switched to ArangoDB 2.1: A new maintenance release for ArangoDB 2.0 is available from the download-corner.

v2.0.8 (2014-05-29)

• fixed too-busy iteration over skiplists Even when a skiplist query was restricted by a limit clause, the skiplist index was queried without the limit. this led to slower-than-necessary execution times.
• fixed timeout overflows on 32 bit systems
• fixed issue #848: db.someEdgeCollection.inEdge does not return correct value when called the 2nd time after a .save to the edge collection this bug has led to problems when select was called with a high timeout value (2000+ seconds) on 32bit systems that don’t have a forgiving select implementation. when the call was made on these systems, select failed so no data would be read or sent over the connection this might have affected some cluster-internal operations.
• fixed ETCD issues on 32 bit systems ETCD was non-functional on 32 bit systems at all. The first call to the watch API crashed it. This was because atomic operations worked on data structures that were not properly aligned on 32 bit systems.