Author Archives: Frank Celler

About Frank Celler

Frank is both entrepreneur and backend developer, developing mostly memory databases for two decades. He is the lead developer of ArangoDB and co-founder of triAGENS. Try to challenge Frank asking him questions on C, C++ and MRuby. Besides Frank organizes Cologne’s nosql group & nosql conferences.

Heartbleeding Windows

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.

Posted in General | Leave a comment

ArangoDB 2.0.2

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

Posted in General, Releases | Leave a comment

ArangoDB 1.4.14

A maintenance release of ArangoDB 1.4 is now available for download. v1.4.14 (2014-04-05) ——————– * fixed race conditions during shape / attribute insertion A race condition could have led to spurios `cannot find attribute #xx` or `cannot find shape #xx` (where xx is a number) warning messages being logged by the server. This happened when a new attribute was inserted and at the same time was queried by another thread. Also fixed a race condition that may have occurred when a thread tried to access the shapes / attributes hash tables while they were resized. In this cases, the shape / attribute may have been hashed to a wrong slot. * fixed a memory barrier / cpu synchronisation problem with libev, affecting Windows with Visual Studio 2013 (probably earlier versions are affected, too) The issue is described in detail here:

Posted in Releases | Leave a comment

ArangoDB 2.0.1

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

Posted in General, Releases | Leave a comment

ArangoDB Sharding Release 2.0.0 RC1

Sharding has come to ArangoDB. We are proud to announce the release candidate of ArangoDB 2.0.0. The ArangoDB 2 is API downward compatible to ArangoDB 1.4. ArangoDB 2 can be used as standalone or distributed system. You can use the same packages / binaries for a stadalone and a sharding setup. See “setup cluster” for how to enable the cluster features of ArangoDB 2 and how to distribute your data to many servers. Please note that the datafiles are not compatible. ArangoDB 2 will convert these files to a newer format. If you only want to play with the new sharding features, make sure that you use a separate database directory. Where to go next? – a general introduction – how set up a distributed cluster – more in-depth information – coming soon: guidelines for API implementors

Posted in Releases | 6 Comments

ArangoDB 1.4.11

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

Posted in General | Leave a comment

ArangoDB 1.4.9

A bug-fix release is available v1.4.9 (2014-02-07) ——————- * return a document’s current etag in response header for HTTP HEAD requests on documents that return an HTTP 412 (precondition failed) error. This allows retrieving the document’s current revision easily. * added AQL function `SKIPLIST` to directly access skiplist indexes from AQL This is a shortcut method to use a skiplist index for retrieving specific documents in indexed order. The function capability is rather limited, but it may be used for several cases to speed up queries. The documents are returned in index order if only one condition is used. /* return all documents with mycollection.created > 12345678 */ FOR doc IN SKIPLIST(mycollection, { created: [[ '>', 12345678 ]] }) RETURN doc /* return first document with mycollection.created > 12345678 */ FOR doc IN SKIPLIST(mycollection, { created: [[ '>', 12345678 ]] }, 0, 1) RETURN doc /* return all documents with mycollection.created between 12345678 and 123456790 */ FOR doc IN SKIPLIST(mycollection, { created: [[ '>', 12345678 ], [ ‘

Posted in Releases | Leave a comment

Cheerio, Node and Coffee-Script

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.

Posted in Foxx, General, Javascript | 2 Comments

ArangoDB 1.4.6

A new release of ArangoDB is available for download.  issue #736: AQL function to parse collection and key from document handle added fm.rescan() method for Foxx-Manager fixed issue #734: foxx cookie and route problem added method `fm.configJson` for arangosh include `startupPath` in result of API `/_api/foxx/config`

Posted in Releases | Leave a comment

ArangoDB 1.4.5

A new release of ArangoDB is available for download. fixed issue #726: Alternate Windows Install Method fixed issue #716: dpkg -P doesn’t remove everything fixed bugs in description of HTTP API `_api/index` fixed issue #732: Rest API GET revision number added missing documentation for several methods in HTTP API `/_api/edge/…` fixed typos in description of HTTP API `_api/document` defer evaluation of AQL subqueries and logical operators (lazy evaluation) Updated font in WebFrontend, it now contains a version that renders properly on windows generally allow function return values as call parameters to AQL functions fixed potential deadlock in global context method execution added override file “arangod.conf.local” (and co)

Posted in Releases | 3 Comments