Skip to content 
ArangoDB 2.1.0 Released: New Features & Enhancements
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…)Meet Lucas in California: ArangoDB Community Event
Lucas (@moonbeamlabs), ArangoDB core developer, rubyist, inventor of Foxx, open source contributor, podcaster etc. – he is currently staying in Mountain View. Yesterday he spoke at the SF JavaScript Meetup at Mozilla and did an introduction to ArangoDB Foxx. Tomorrow he will give a lightening talk about Guacamole at the San Francisco Ruby on Rails Group.
And yes, you can have Lucas at your user group/meetup as well. He is not only speaking on Foxx and ArangoDB, but also on Guacamole, an ORM for Rails, and also on “NoSQL and Domain Driven Design”. You can easily contact Lucas via twitter or send an e-mail to hackers at arangodb.com.
ArangoDB 2.1 RC 1: Test the Latest Features | ArangoDB
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…)
Heartbleed Bug: Impact on Windows Users | ArangoDB Insights
I assume you all heard about the Heartbleed Bug in OpenSSL. ArangoDB uses the system OpenSSL under linux and Mac OS. If you update your version to 1.0.1g or better, everything is fine.
However, the Windows contains static version of OpenSSL. So in case you want to use ArangoDB with HTTPS, you should update your ArangoDB version. The current installer for 1.4.14 and 2.0.2 contains the OpenSSL 1.0.1g.
ArangoDB 2.0.2 Release: Enhancements & Bug Fixes
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
ArangoDB 2.0.1 Release: Enhancements & Bug Fixes
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 choiceArangoDB 1.4.11 Release: Enhancements & Bug Fixes
We have released a bug-fix release for ArangoDB 1.4. As it is carnival, we skipped 1.4.10 and moved directly to 1.4.11. Please note that we are also preparing the ArangoDB 2.0 release. Therefore it is important to use the
zypper install arangodb=1.4.11
(or whatever package manager you use) with an explicit version.
v1.4.11 (2014-02-27)
--------------------
* added SHORTEST_PATH AQL function
this calculates the shortest paths between two vertices, using the Dijkstra
algorithm, employing a min-heap
By default, ArangoDB does not know the distance between any two vertices and
will use a default distance of 1. A custom distance function can be registered
as an AQL user function to make the distance calculation use any document
attributes or custom logic:
RETURN SHORTEST_PATH(cities, motorways, "cities/CGN", "cities/MUC", "outbound", {
paths: true,
distance: "myfunctions::citydistance"
})
// using the following custom distance function
var aqlfunctions = require("org/arangodb/aql/functions");
aqlfunctions.register("myfunctions::distance", function (config, vertex1, vertex2, edge) {
return Math.sqrt(Math.pow(vertex1.x - vertex2.x) + Math.pow(vertex1.y - vertex2.y));
}, false);
* fixed bug in Graph.pathTo function
* fixed small memleak in AQL optimiser
* fixed access to potentially uninitialised variable when collection had a cap constraint
v1.4.10 (2014-02-21)
--------------------
* fixed graph constructor to allow graph with some parameter to be used
* added node.js "events" and "stream"
* updated npm packages
* added loading of .json file
* Fixed http return code in graph api with waitForSync parameter.
* Fixed documentation in graph, simple and index api.
* removed 2 tests due to change in ruby library.
* issue #756: set access-control-expose-headers on CORS response
the following headers are now whitelisted by ArangoDB in CORS responses:
- etag
- content-encoding
- content-length
- location
- x-arango-errors
- x-arango-async-id
Cheerio with Node.js and CoffeeScript | ArangoDB Tutorial
Foxx’ main purpose is to create a beautiful API for your AngularJS, EmberJS or Backbone.js front-end. However, sometimes you want to do more. We, for example, needed to parse some HTML files. ArangoDB is capable of using some Node.js modules, but unfortunately Cheerio was not one of those. One problem was that we did not support loading of JSON data modules. So, this was a good excuse to rewrite the module loader in ArangoDB to make it even more Node.js-friendly.
With those improvements, that are currently available in ArangoDB’s devel branch. You can now also “require” a JSON data file. These files must have a filename ending with “.json”. If the filename ends with “.coffee” it is treated as coffee-script file and automatically compiled into JavaScript.
A Foxx app can now contain its own “node_modules” directory to include Node modules which it requires. This makes it much easier to deploy a Foxx app.
ArangoDB at FOSDEM 2014: Insights & Presentations
FOSDEM is an absolutely open and free conference in Brussels, Belgium. The conference offers an impressive amount of developer rooms discussing a broad range of technical topics, including NoSQL and graphs.
After a funny and productive ArangoDB hackathon weekend Frank and I arrived at FOSDEM on Sunday noon. We were looking forward to the talks in the graph devroom, but unfortunately for us it was not possible to enter the room (it was overfull, indicating a great quality of talks).
At the next speakers change Frank and I managed to slip into the room and could enjoy two inspiring talks by Neo4J.
Afterwards it was my turn to present the graph visualization interface in ArangoDB in a still crowded room (slides).
After my presentation, we handed out all our ArangoDB t-shirts to our fans.
Michael handing out T-Shirts to the audience
All together it was a great experience and a really huge amount of people visiting the same conference which impressed me a lot.
Thanks for the team at the Graph Processing devroom for giving me the opportunity to speak and for organizing such a great devroom.
We will meet again next year.
so long,
Michael
ArangoDB’s Web Interface Screencast | Explore Management Tools
With ArangoDB we ship a nice and useful web interface for administration.
However we have not yet told you in a video what you can do with this interface.
This screencast will give a comprehensive overview over the features offered in the interface.
Get the latest tutorials,
blog posts and news: