ArangoDB 1.4.11
Estimated reading time: 1 minutes
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

Leave a Comment