Links

Submitted by

Update

Share project

ArangoDB is a multi-model, open-source database with flexible data models for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions. Use ACID transactions if you require them.
The supported data models can be mixed in queries and allow ArangoDB to be the aggregation point for your data.
Key Features in ArangoDB
- Multi-Model: Documents, graphs and key-value pairs — model your data as you see fit for your application.
- Joins: Conveniently join what belongs together for flexible ad-hoc querying, less data redundancy.
- Transactions: Easy application development keeping your data consistent and safe. No hassle in your client.

Recent Releases

3.2.309 Sep 2017 03:18minor bugfix:
: orphan collections could not be registered in general-graph module.
Wrong selection of the database inside the internal cluster js api.
Added startup option `--server.check-max-memory-mappings` to make arangod check.
The number of memory mappings currently used by the process and compare it with
The maximum number of allowed mappings as determined by /proc/sys/vm/max_map_count
Note that this option is effective on Linux systems only.
Wrong ui cluster health information.
: HTTP Foxx API Json parsing.
: Foxx queue: job isn't running when server.authentication = true.
Supervision failure detection and handling, which happened with simultaneous agency leadership change.

3.2.225 Aug 2017 03:15minor bugfix:
: adjust the response of the DELETE `/_api/users/database/*` calls.
: Error when upgrading arangoDB on linux ubuntu 16.04.
a buffer overrun in linenoise console input library for long input strings.
Increase size of the linenoise input buffer to 8 KB.
Abort compilation if the detected GCC or CLANG isn't in the range of compilers
we support.
Spurious cluster hangups by always sending AQL-query related requests
to the correct servers, even after failover or when a follower drops.
The problem with the previous shard-based approach was that responsibilities.
For shards may change from one server to another at runtime, after the query
Was already instanciated. The coordinator and other parts of the query then
Sent further requests for the query to the servers now responsible for the
Shards.
However, an AQL query must send all further requests to the same servers on.
Which the query was originally instanciated, even in case of failover.
Otherwise this would potentially send requests to servers that do not know.
About the query, and would also send query shutdown requests to the wrong
Servers, leading to abandoned queries piling up and using resources until
They automatically time out.
With RocksDB engine acquiring the collection count values too.
Early, leading to the collection count values potentially being slightly off
Even in exclusive transactions (for which the exclusive access should provide
an always-correct count value).
Some in leader-follower catch-up code, specifically for the
RocksDB engine.
Make V8 log fatal errors to syslog before it terminates the process.
This change is effective on Linux only.
With MMFiles engine creating superfluous collection journals
on shutdown.
: Upgrade from 3.2 to 3.2.1 reset autoincrement keys.
: ArangoDB server shutdown unexpectedly.
: Incorrect filter interpretation.
: Foxx, internal server error when I try to add a new service.
Improved MMFiles fulltext index document removal performance.
And

3.2.112 Aug 2017 03:17minor bugfix:
: Optimizer rule reduce-extraction-to-projection breaks queries.
Now allowing to restore users in a sharded environment as well
It is still not possible to restore collections that are sharded.
Differently than by _key.
an isse with restoring of system collections and user rights.
It was not possible to restore users into an authenticated server.
: Documentation for db._createDatabase is wrong.
ui: added bind parameters to slow query history view.
: Slow Query API should provide bind parameters, webui should display them.
ui: a when moving multiple documents was not possible.
Docs for : Collection _key autoincrement value increases on error.
AQL CHAR_LENGTH(null) returns now 0. Since AQL TO_STRING(null) is '' (string of length 0).
ui: now supports single js file upload for Foxx services in addition to zip files.
a multi-threading in the agency when callElection was called.
While the Supervision was calling updateSnapshot
Added startup option `--query.tracking-with-bindvars`.
This option controls whether the list of currently running queries.
And the list of slow queries should contain the bind variables used
in the queries or not.
The option can be changed at runtime using the commands.
// enables tracking of bind variables.
// set to false to turn tracking of bind variables off.
Var value = true;
Require("@arangodb/aql/queries").properties(
TrackBindVars: value
);.
Index selectivity estimates are now available in the cluster as well.
: loadIndexesIntoMemory not returning the same structure
as the rest of the collection APIs.
: ArangoError 1208: illegal name.
: Collection properties do not return `isVolatile`.
Attribute
Potential for : Segmentation fault when starting.
Coordinator node
: out of memory error when running UPDATE/REPLACE
on medium-size collection.
Potential deadlock errors in collector thread.
Disallow the usage of volatile collections in the RocksDB engine
by throwing an error when a collection

3.1.2321 Jun 2017 03:15minor bugfix:
Potentially : Duplicate _key generated on insertion.
Races in SSL communication code.
Invalid results (too many) when a skipping LIMIT was used for a.
Traversal. `LIMIT x` or `LIMIT 0, x` were not affected, but `LIMIT s, x`
May have returned too many results
Invalid first group results for sorted AQL COLLECT when LIMIT.
Was used
Invalid locking in JWT authentication cache, which could have.
Crashed the server
Undefined behavior in traverser when traversals were used inside
a FOR loop.

3.1.2017 May 2017 03:15minor bugfix:
Incorrect sorting for distributeShardsLike.
Improve reliability of AgencyComm communication with Agency.
Shard numbering, where ids were erouneously incremented by 1.
Remove an unnecessary precondition in createCollectionCoordinator.
Funny fail rotation.
in SimpleHttpClient for correct advancement of readBufferOffset.
Forward SIG_HUP in supervisor process to the server process to logrotaion
You need to stop the remaining arangod server process manually for the upgrade to work.

3.1.1903 May 2017 03:15minor bugfix:
: GraphBrowser "Expand" function doesn't load all possible edges.
: Intermittent where ArangoDB Web UI takes no action when Delete button is clicked for a document.
: Frontend shows already deleted databases during login.
Added 'x-content-type-options: nosniff' to avoid MSIE.
: dead/old link in foxx-manager help.
: Indexing break replication.
a StackOverflow in Traversal and ShortestPath. Occured if many ( 1000) input.
Values in a row do not return any result. occasional hanging shutdowns on OS X
Reduce the maximal wait time in exponential backoff when waiting for locks.
This improves fairness of the collection locks under high load.

3.1.1821 Apr 2017 03:15minor bugfix:
Error in continuous synchronization of collections.
Spurious hangs on server shutdown.
Better error messages during restore collection.
Completely overhaul supervision. More detailed tests.
a dead-lock situation in cluster traversers, it could happen in.
Rare cases if the computation on one DBServer could be completed much earlier
Than the other server. It could also be restricted to SmartGraphs only.
(Enterprise only) a in SmartGraph DepthFirstSearch. In some.
More complicated queries, the maxDepth limit of 1 was not considered strictly
Enough, causing the traverser to do unlimited depth searches.
.

3.1.1705 Apr 2017 03:15minor bugfix:
(Enterprise only) a where replicationFactor was not correctly.
Forwarded in SmartGraph creation.
this restores the default read-cache size value for RAM sizes of less than
4 GB to the default size the read cache had in 3.1.15 and before. 3.1.16.
Decreased the default value too much for small RAM sizes.
ui - smart graph option not appearing.
.

3.1.1308 Mar 2017 06:45minor bugfix:
variables parsing in GraphQL.
changed thread handling to queue only user requests on coordinator.
Use exponential backoff when waiting for collection locks.
Repair short name server lookup in cluster in the case of a removed.
Server

3.1.1201 Mar 2017 09:25minor bugfix:
Disable shell color escape sequences on Windows.
a race condition when closing a connection.
Raised default hard limit on threads for very small to 64.
Negative counting of http connection in UI.
a race when renaming collections.
a race when dropping databases.
a rare race in agency compaction.

3.1.1116 Feb 2017 06:45minor bugfix:
ui: optimized smart graph creation usability.
ui: a race in async task cancellation via `require("@arangodb/tasks").unregisterTask()`.
Spuriously hanging threads in cluster AQL that could sit idle for a few minutes.
Potential numeric overflow for big index ids in index deletion API.
Sort in cluster, occurring when one of the local sort buffers of a
GatherNode was empty.
Reduce number of HTTP requests made for certain kinds of join queries in cluster.
Leading to speedup of some join queries
Supervision deals with demised coordinators correctly again.
Implement a timeout in TraverserEngineRegistry.
Agent communication reduced in large batches of append entries RPCs.
Inception no longer estimates RAFT timings.
Compaction in agents has been moved to a separate thread.
Replicated logs hold local timestamps.
Supervision jobs failed leader and failed follower revisited for.
Function in precarious stability situations
Big in random number generator for 64bit int.

3.1.410 Dec 2016 03:15minor feature:
at cluster start, coordinators wait until at least one DBserver is there.
And either at least two DBservers are there or 15s have passed, before they
Initiate the bootstrap of system collections.
More robust agency startup from devel.
Supervision's AddFollower adds many followers at once.
Supercision has new FailedFollower job.
Agency's Node has new method getArray.
Agency RAFT timing estimates more conservative in waitForSync.
Scenario
Agency RAFT timing estimates capped at maximum 2.0/10.0 for low/high.

3.1.229 Nov 2016 08:05minor bugfix:
Save a flag in the agency indicating that the system collection were created.
This prevents hanging coordinators during startup when the system collections
Got into a bad state somehow
Adjust server failed job so it will cancel any shard movement jobs.
When a server became healthy again
Improve several cluster related log messages.
Added support for descriptions field in Foxx dependencies.
Enforce a user defined jwt when doing authentication in the cluster.
a in the agency inception visible only under Windows. One has
to wait until the RestServer maintenance mode is off, before we start.
The gossip protocol to find peers.
(Enterprise only) a in the statistic report for SmartGraph traversals.
Now they state correctly how many documents were fetched from the index and how many.
Have been filtered.
Increments of version in agent configurations.
Startup mode of agency is explicitly set to persistence with inside.
Agent configuration
Statistics for requests.
Race condition in processing of VelocyStream (vst) binary protocol.

3.1.124 Nov 2016 03:15minor bugfix:
Obsolete --cluster.username and --cluster.password.
display index usage of traversals in AQL explainer output (previously missing).
Isuse #2163.
Preserve last-used HLC value across server starts.
Allow more control over handling of pre-3.1 _rev values.
This changes the server startup option `--database.check-30-revisions` from a boolean (true/false).
Parameter to a string parameter with the following possible values:
- "fail":
Will validate _rev values of 3.0 collections on collection loading and throw an exception when invalid _rev values are found.
in this case collections with invalid _rev values are marked as corrupted and cannot be used in the ArangoDB 3.1 instance.
The procedure for such collections is to export the collections from 3.0 database with arangodump and restore them in 3.1 with arangorestore.
Collections that do not contain invalid _rev values are marked as ok and will not be re-checked on following loads.
Collections that contain invalid _rev values will be re-checked on following loads.
- "true":
Will validate _rev values of 3.0 collections on collection loading and print a warning when invalid _rev values are found.
in this case collections with invalid _rev values can be used in the ArangoDB 3.1 instance.
However, subsequent operations on documents with invalid _rev values may silently fail or fail with explicit errors.
The procedure for such collections is to export the collections from 3.0 database with arangodump and restore them in 3.1 with arangorestore.
Collections that do not contain invalid _rev values are marked as ok and will not be re-checked on following loads.
Collections that contain invalid _rev values will be re-checked on following loads.
- "false":
Will not validate _rev values on collection loading and not print warnings.
no hint is given when invalid _rev values are found.
Subsequent operations on documents with invalid _rev values may silently fail or fail with explicit errors.
This setting does not af

2.6.224 Jul 2015 10:03minor bugfix:
* fixed issue #1383: bindVars for HTTP API doesn't work with empty string
* fixed handling of default values in Foxx manifest configurations
* fixed handling of optional parameters in Foxx manifest configurations
* fixed a reference error being thrown in Foxx queues when a function-based job type is used that is not available and no options object is passed to queue.push