This version is deprecated. Download the new version of ArangoDB

Dear ArangoDB users,

we are proud to announce the official release of ArangoDB 2.1. It is a major step forward containing a lot of improvements. If you are upgrading from ArangoDB 2.0, please read the upgrade notes carefully.

Kind regards Frank

(more…)

Dear ArangoDB users,

we are proud to announce the first release candidate for ArangoDB 2.1 two months after the first sharding release 2.0. It is a major step forward containing a lot of improvements.

Please note that we need your help testing the release candidate for any glitches and bugs. For instance, we moved to C++11. We tested the RPM and DEB packages we have built, but as there are so many different set-ups we certainly did not find all incompatibilities.

You can download packages from our website. Please report any bugs to us using the issue tracker of Github.

Thanks in advance for your help
Frank
(more…)

This version is deprecated. Download the new version of ArangoDB

We have released a bug-fix release for ArangoDB 2.0.

v2.0.2 (2014-04-06)

• during cluster startup, do not log (somewhat expected) connection errors with log level error, but with log level info
• fixed dashboard modals
• fixed connection check for cluster planning front end: firefox does not support async:false
• document how to persist a cluster plan in order to relaunch an existing cluster later
• added REST API method HTTP GET `/_api/job/job-id` to query the status of an async job without potentially fetching it from the list of done jobs
• fixed non-intuitive behaviour in jobs API: previously, querying the status of an async job via the API HTTP PUT `/_api/job/job-id` removed a currently executing async job from the list of queryable jobs on the server. Now, when querying the result of an async job that is still executing, the job is kept in the list of queryable jobs so its result can be fetched by a subsequent request.
• improve documentation of db._create and explain the rules and limitations following from the choice of shardKeys for sharded collections with more than one shard

This version is deprecated. Download the new version of ArangoDB

We have just release 2.0.1, which is bug-fix release for 2.0.

v2.0.1 (2014-03-31) ——————- * make ArangoDB not send back a `WWW-Authenticate` header to a client in case the client sends the `X-Omit-WWW-Authenticate` HTTP header. This is done to prevent browsers from showing their built-in HTTP authentication dialog for AJAX requests that require authentication. ArangoDB will still return an HTTP 401 (Unauthorized) if the request doesn’t contain valid credentials, but it will omit the `WWW-Authenticate` header, allowing clients to bypass the browser’s authentication dialog. * fixed isses in arango-dfdb: the dfdb was not able to unload certain system collections, so these couldn’t be inspected with the dfdb sometimes. Additionally, it did not truncate corrupt markers from datafiles under some circumstances * added `changePassword` attribute for users * fixed non-working “save” button in collection edit view of web interface clicking the save button did nothing. one had to press enter in one of the input fields to send modified form data * fixed V8 compile error on MacOS X * prevent `body length: -9223372036854775808` being logged in development mode for some Foxx HTTP responses * fixed several bugs in web interface dashboard * fixed issue #783: coffee script not working in manifest file * fixed issue #781: Cant save current query from AQL editor ui * bumped version in `X-Arango-Version` compatibility header sent by arangosh and other client tools from `1.5` to `2.0`. * fixed startup options for arango-dfdb, added details option for arango-dfdb * fixed display of missing error messages and codes in arangosh * when creating a collection via the web interface, the collection type was always “document”, regardless of the user’s choice