ArangoDB Changelog

What's new in ArangoDB 3.7.3

Oct 21, 2020

Added the following metrics for synchronous replication in the cluster:
`arangodb_refused_followers_count`: Number of times a shard leader received a refusal answer from a follower during synchronous replication.
`arangodb_sync_wrong_checksum`: Number of times a mismatching shard checksum was detected when syncing shards. In case this happens, a resync will be triggered for the shard.
Fixed handling of failedLeaderJob. In case of a plan modification, that removes a server from the plan, e.g. reduce replication factor. Directly followed by a failure of the current shard leader, would reinsert the just removed server in the plan, which is undesired, we first need to have a full "desync" cycle on this server to be reusable in the plan again.
Make sure the optimizer doesn't pick another index than the TTL index itself while fulfilling the expiry of TTL.
Added optional verbose logging for agency write operations. This logging is configurable by using the new log topic "agencystore".
The following log levels can be used for for the "agencystore" log topic to log writes to the agency:
DEBUG: will log all writes on the leader
TRACE: will log all writes on both leaders and followers
The default log level for the "agencystore" log topic is WARN, meaning no agency writes will be logged.
Turning on this logging can be used for auditing and debugging, but it is not recommended in the general case, as it can lead to large amounts of data being logged, which can have a performance impact and will lead to higher disk space usage.
Print image base address and CPU context (if available) in crash handler messages.
Added configuration option `--query.tracking-slow-queries` to decide whether slow queries are tracked extra.
Added configuration option `--query.tracking-with-querystring` to decide whether the query string is shown in the slow query log and the list of currently running queries. The option is true by default.
When turned off, querystrings in the slow query log and the list of currently running queries are just shown as "".
Added configuration option `--query.tracking-with-datasources` to toggle whether the names of data sources used by queries are shown in the slow query log and the list of currently running queries. The option is false by default.
When turned on, the names of data sources used by the query will be shown in the slow query log and the list of currently running queries.
Fixed handling of failoverCandidates. Sometimes, a server can still be a failoverCandidate even though it has been taken out of the Plan. With this fix, such a server is quickly taken out of failoverCandidates and it can never be re-added to the Plan before this has happened.
Fix #12693: SORT inside a subquery could sometimes swallow part of its input when it crossed boundaries of internal row batches.
Fixed issue BTS-212: Web UI doesn't let to make partial view update and partial view update should be audited (also reported as ES-700).
Fixed link definition comparison logic: equality wasn`t properly detected and led to link recreation.
Added configuration option `--rocksdb.sync-delay-threshold`.
This option can be used to track if any RocksDB WAL sync operations is delayed by more than the configured value (in milliseconds). The intention is to get aware of severely delayed WAL sync operations.
Add database, shard name and error information to several shard-related log messages.
Display shard names of a collection in the web interface when in the details view of the collection.
Added HTTP requests metrics for tracking the number of superuser and normal user requests separately:
`arangodb_http_request_statistics_superuser_requests`: Total number of HTTP requests executed by superuser/JWT
`arangodb_http_request_statistics_user_requests`: Total number of HTTP requests executed by clients
Fixed a bug in handling of followers which refuse to replicate operations.
In the case that the follower has simply been dropped in the meantime, we now avoid an error reported by the shard leader.
Fix a performance regression when a LIMIT is combined with a COLLECT WITH COUNT INTO. Reported in ES-692.
Fix REST handler GET /_admin/status when called with URL parameter value `overview=true`. For generating the `hash` attribute in the response, the current Plan was retrieved and analyzed. Due to a change in the internal Plan format the REST handler code failed to pick up the number of servers, which resulted in the REST handler returning HTTP 500 in cluster mode.
Use rclone built from v1.51.0 source with go1.15.2 instead of prebuilt v1.51.0 release.
Fixed a bug in AQL COLLECT with OPTIONS { "hash" } that lead to a quadratic runtime in the number of output rows.
Added startup option `--database.old-system-collections` to toggle automatic creation of system collections `_modules` and `_fishbowl`, along with their internal usage. These collections are useful only in very few cases, so it is normally not worth to create them in all databases.
The `_modules` collection is only used to register custom JavaScript modules, for which there exists no API, and `_fishbowl` is used to store the temporary list of Foxx apps retrieved from the Github Foxx store.
If the option value is `false` (which is the default from v3.8 onwards, but for v3.7 the default value is `true` for downwards-compatibility), the two collections will not be created for any new database. The `_fishbowl`collection will still be created dynamically when needed. If the option value is `true` (the default value in v3.7), the collections will be created regularly as before.
The default value for the option is going to change to `false` in v3.8, meaning the collections will not be created anymore there by default.
Any functionality related to the `_modules` system collection is deprecate and will be removed in ArangoDB v3.9.
Two side effects of turning this option off are:
there will no be iteration over all databases at server startup just to check the contents of all `_modules` collections.
less collections/shards will be around for deployments that create a large number of databases.
Already existing `_modules` and `_fishbowl` system collections will not be modified by this PR, even though they will likely be empty and unused.
Don't iterate over all databases as server startup in order to initialize the routing information. This is not necessary, as the routing information is global and not tied to a specific database.
Fixed a possible crash during instantiation of an AQL graph traversal. Reported in #12597.
Added safeguards against using V8 internally in environments that have JavaScript turned off via the `--javascript.enabled false` option.
Make scheduler propertly count down the number of working threads in case an exception happens in a worker thread.
Turn off upgrade checks in arangod in alpha/beta/preview Enterprise builds, too.
Previously it was already turned off in arangod for Enterprise builds already, but only for stable releases and not preview releases.
Fixed and extended LDAP log messages.
Added LDAP_OFF if referrals and restart are false.
If LDAP search fails, also retry (update to given number of retries).
Fixed inifinite reload of the login window after logout of an LDAP user.
Make the reboot tracker catch failed coordinators, too. Previously the reboot tracker was invoked only when a DB server failed or was restarted, and when a coordinator was restarted. Now it will also act if a coordinator just fails (without restart).
Added scheduler thread creation/destruction metrics:
`arangodb_scheduler_threads_started`: Number of scheduler threads started
`arangodb_scheduler_threads_stopped`: Number of scheduler threads stopped
Added startup option `--query.max-runtime` to limit the maximum runtime of all
AQL queries to a specified threshold value (in seconds). By default, the threshold is 0, meaning that the runtime of AQL queries is not limited.
Setting it to any positive value will restrict the runtime of all AQL queries unless it is overwritten in the per-query "maxRuntime" query option.
Please note that setting this option will affect *all* queries in all databases, and also queries issues for administration and database-internal purposes.
If a query exceeds the configured runtime, it will be killed on the next occasion when the query checks its own status. Killing is best effort, so it is not guaranteed that a query will no longer than exactly the configured amount of time.
Ensure that the argument to an AQL OPTIONS clause is always an object which
does not contain any dynamic (run-time) values. Previously, this was only enforced for traversal options and options for data-modification queries. This change extends the check to all occurrences of OPTIONS.
Added `details` option to figures command of a collection:
`collection.figures(details)`
Setting `details` to `true` will return extended storage engine-specific details to the figures. The details are intended for debugging ArangoDB itself and their format is subject to change. There is not much use in using the details from a client application.
By default, `details` is set to `false`, so no details are returned and the behavior is identical to previous versions of ArangoDB.
Implement RebootTracker usage for AQL queries in case of coordinator restarts or failures. This will clean up the rest of an AQL query on dbservers more quickly and in particular release locks faster.
Serialize maintenance actions for each shard. This addresses lost document problems found in chaos testing.
Enforce a maximum result register usage limit in AQL queries. In an AQL query, every user-defined or internal (unnamed) variable will need a register to store results in.
AQL queries that use more result registers than allowed (currently 1000) will now abort deterministically during the planning stage with error 32 (`resource limit exceeded`) and the error message "too many registers (1000) needed for AQL query".
Before this fix, an AQL query that used more than 1000 result registers crashed the server when assertions were turned on, and the behavior was undefined when assertions were turned off.
Fixed some cases where subqueries in PRUNE did not result in a parse error, but either in an incomprehensible error (in 3.7), or undefined behaviour during execution (pre 3.7).
Fixed an issue with audit logging misreporting some document requests as internal instead of logging the proper request information.
Add attributes `database` and `user` when tracking current and slow AQL queries.
`database` contains the name of the database the query is/was running in, `user` contains the name of the user that started the query.
These attributes will be returned in addition when calling the APIs for current and slow query inspection:
GET `/_api/query/current` and `require("arangodb/aql/queries").current()`
GET `/_api/query/slow` and `require("arangodb/aql/queries").slow()`
The "slow query" log message has also been augmented to contain the database name and the user name.
The `user` attribute is now also displayed in the web interface in the "Running queries" and "Slow queries" views.
Added metrics for V8 contexts usage:
`arangodb_v8_context_alive`: number of V8 contexts currently alive.
`arangodb_v8_context_busy`: number of V8 contexts currently busy.
`arangodb_v8_context_dirty`: number of V8 contexts currently dirty.
`arangodb_v8_context_free`: number of V8 contexts currently free.
`arangodb_v8_context_max`: maximum number of concurrent V8 contexts.
`arangodb_v8_context_min`: minimum number of concurrent V8 contexts.
Updated arangosync to 0.7.11.
Make followers in active failover run a compaction after they process a truncate operation and the truncate removed more than 4k documents. This can help to reclaim disk space on the follower earlier than without running the truncate.
The REST API PUT `/_api/collection//truncate` will now also run a compaction if the truncation affected more than 4k documents. This may add extra latency to the truncate operation, but can help to reclaim disk space earlier.
Added REST API PUT `/_admin/compact` for compacting the entire database data.
This endpoint can be used to reclaim disk space after substantial data deletions have taken place. The command is also exposed via the JavaScript API as `db._compact();`.
This command can cause a full rewrite of all data in all databases, which may take very long for large databases. It should thus only be used with care and only when additional I/O load can be tolerated for a prolonged time.
This command requires superuser access and is only available for the RocksDB storage engine.
Don't allow creation of smart satellite graphs or collections (i.e. using `"isSmart":true` together with `"replicationFactor":"satellite"` when creating graphs or collections. This combination of parameters makes no sense, so that the server will now respond with "bad parameter" and an HTTP status code of HTTP 400 ("Bad request").
Add exit code for ICU database loading startup errors.
Fixed issue #12507: SegFault when using an AQL for loop through edges.
Make the `IS_IPV4` AQL function behave identical on macOS as on other platforms. It previously allowed leading zeros in octets on macOS, whereas on other platforms they were disallowed. Now this is disallowed on macOS as well.
Added new metric "arangodb_aql_slow_query" for slow AQL queries, so this can be monitored more easily.
Added new metric "arangodb_scheduler_queue_length" for the scheduler's internal queue length.
Added new metric "arangodb_scheduler_queue_full_failures" for tracking cases of a full scheduler queue and dropping requests.
Added new metrics for the number of V8 contexts dynamically created and destroyed ("arangodb_v8_context_created" and "arangodb_v8_context_destroyed")
and for the number of times a V8 context was entered and left ("arangodb_v8_context_entered" and "arangodb_v8_context_exited"). There is
also a new metric for tracking the cases when a V8 context cannot be successfully acquired and an operation is not performed ("arangodb_v8_context_enter_failures").
Added extra info to "queue full" and "giving up waiting for unused v8 context" log messages.
Request to the `/_admin/statistics` API now processed via the CLIENT_FAST lane.
Previously they were handled in the CLIENT_SLOW lane, meaning that monitoring requests using that API didn't get through when the queue was rather full.
Introduce an internal high-water mark for the maximum row number that was written to in an AqlItemBlock. Using this number several operations on the whole block, such as cleaning up or copying can be made more efficient when run on only partially filled blocks.
Fixed issue BTS-169: cost estimation for LIMIT nodes showed wrong number of estimated items.

New in ArangoDB 3.7.2.1 (Sep 17, 2020)

New in ArangoDB 3.7.2 (Aug 27, 2020)

ixed internal issue #744: LIMIT with only offset and constrained heap optimization will use estimation value for ArangoSearch views.
Make UPSERT statement with collection bind parameter behave identical to its non-bind parameter counterpart.
with a hard-coded collection name would succeed. This is now fixed so both queries have the same behavior (no failure) in single server.
Updated arangosync to 0.7.10.
Fixed internal issue #742: Add tick storage in index meta payload for ArangoSearch view links after collection truncate operation.
Fixed issue #12304: insert in transaction causing com.arangodb.ArangoDBException: Response: 500, Error: 4 - Builder value not yet sealed.
This happened when too deeply-nested documents (more than 63 levels of nesting) were inserted. While indefinite nesting is still not supported, the error message has been corrected from the internal HTTP 500 error "Builder value not yet sealed" to the correct HTTP 400 "Bad parameter".
Fixed: During a move-shard job which moves the leader there is a situation in which the old owner of a shard can reclaim ownership (after having resigned already), with a small race where it allows to write documents only locally, but then continue the move-shard to a server without those documents. An additional bug in the MoveShard
Supervision job would then leave the shard in a bad configuration with a resigned leader permanently in charge.
Fixed a problem with potentially lost updates because a failover could happen at a wrong time or a restarted leader could come back at an unlucky time.
Fixed BTS-167: Lingering Queries - Canceled from the UI.
This fixes queries not vanishing from the list of running queries in the web UI in case the query was canceled using the "Cancel" button in web UI's query editor.
Fixed bad behaviour in agency supervision in some corner cases involving already resigned leaders in Current.
Fixed issue ES-664: the optimizer rule `inline-subqueries` must not pull out subqueries that contain a COLLECT statement if the subquery is itself called from within a loop. Otherwise the COLLECT will be applied to the values in the outer FOR loop, which can produce a different result.
Fixed that dropping a vanished follower works again. An exception response to the replication request is now handled properly.
Make AQL user-defined functions (UDFs) work in a cluster in case the UDF runs an AQL query inside its own function code (BTS-159).
Fixed hotbackup S3 credentials validation and error reporting for upload and download.
Fixed a blockage on hotbackup when writes are happening concurrently, since followers could no longer replicate leader transactions.
Fix: The 'sorted' COLLECT variant would return undefined instead of null when grouping by a null value.
Fix: writeConcern is now honored correctly (ES-655).
Fixed internal issue #739: ArangoSearch filter volatility takes into account calculation nodes dependencies.
Fixed OASIS-278 issue: Added proper sort/calc nodes cleanup for late materialzation after OneShard optimization.
Slightly improve the performance of cluster DDL maintenance operations.
Added AQL functions `IS_IPV4`, `IPV4_TO_NUMBER`, `IPV4_FROM_NUMBER` for IPv4 address checks and conversions.
Added AQL function `PRODUCT` to calculate the product of an array.
Improve performance of internal cluster Plan and Current reload operations.
Fixed issue #12349: arangosh compact Arangoerror 404.
Improve performance of many non-subquery AQL queries, by optimizing away some storage overhead for subquery context data.
Always fetch data for /_api/cluster/agency-dump from leader of the agency. Add option "redirectToLeader=true" to internal /_api/agency/state API.
Fixed regression with view use-after-create in cluster (BTS-137).
Slightly improved the performance of some k-shortest-path queries.

New in ArangoDB 3.6.5 (Jul 19, 2020)

Updated arangosync to 0.7.8.
Added missing state rollback for failed attempt-based write locking of spin locks.
Fixed a sleeping barber in Fuerte HTTPConnection. It was possible that sendRequest calls were started but never completed due to the fact that the idle connection close triggered at exactly the same time.
Fixed potentially undefined behavior in syslog logger, with ident string going out of scope after `openlog` was called.
Fix cluster-internal request forwarding for VST requests that do not have any Content-Type header set. Such requests could have been caused by the Java driver (ES-635).
Added vertex validation in case of a SmartGraph edge definition update.
Fix untenable ultra precondition for removeServer.
Fixed that the hotbackup agency lock is released under all circumstances using scope guards. This addresses a rare case in which the lock was left behind.
Internal issue BTS-71: Added a precondition to prevent creating a collection with an invalid `distributeShardsLike` property.
Reinstate longer retention period for agency history (step size back to 1000, keep size back to 50000).
Internal issue BTS-71: In a cluster, for collections in creation, suspend supervision jobs concerning replication factor until creation is completed. Previously, it could cause collection creation to fail (e.g. when a server failed during creation), even when it didn't have to.
Internal issue BTS-71: Fixed error handling regarding communication with the agency. This could in a specific case cause collection creation in a cluster report success when it failed.
Fixed a document parsing bug in the Web UI. This issue occured in the document list view in case a document had an attribute called `length`. The result was an incorrect representation of the document preview.
The Web UI now displays an error message inside the node information view in case the user has no access to retreive the neccessary information.
Fixed a potential agency crash if trace logging is on.
Add more context error messages in certain agency failure situations in debug/trace mode.
Fixed issue OASIS-252: Hotbackup agency locks without clientId.
Correct some log entries.
Fixed BTS-110: Fulltext index with minLength

New in ArangoDB 3.6.4 (Jun 2, 2020)

New in ArangoDB 3.6.3.1 (May 7, 2020)

New in ArangoDB 3.6.3 (May 7, 2020)

Fixed internal issue #686: 'docs out of order' error during ArangoSearch consolidation.
Fixed a bug which occurred if a dbserver was shut down exactly when it was supposed to resign from its leadership for a shard.
Fixed internal issue ES-544.2: non-terminating queries could occur when an ArangoSearch view would be accessed inside a spliced subquery with no indexed documents on one DBServer that was part of the query.
Updated OpenSSL to 1.1.1f.
Improve continuation behavior of AQL queries. We post the continuation handler on lane CLUSTER_AQL instead of CLIENT_AQL. This leads to MEDIUM prio instead of LOW.
When relaying requests to other coordinators in a load-balanced setup, don't forward the "http/1.1" HTTP header from the remote response. Forwarding that header in the same way as any other header is not required, as each response will store and set its status separately anyway. Adding it to the headers again will only cause confusion and some client applications to choke.
Don't invoke collection key ranges compaction after performing a truncate operation on a RocksDB storage engine collection via the REST API's truncate endpoint.
The compaction was previously done to make RocksDB physically free data of key ranges that were supposed to be empty after the truncate, but it seems that the used version of RocksDB is struggling to achieve that goal. Although it does compact the ranges, it seems to read a lot of extra data from unrelated ranges as well, which blows up the overall time required to do the compactions.
Most recent versions of RocksDB do not seem to have this problem anymore. But without upgrading RocksDB to the latest version the most sensible fix is to turn off the manual compaction and rely on RocksDB eventually freeing the key ranges that are empty after a truncate.
Avoid some unnecessary internal calls to the storage engine during the incremental sync protocol for the RocksDB storage engine. This change can help reduce the I/O load on the follower during incremental sync for the RocksDB storage engine.
Fixed issue #11104: `ANALYZER` function doesn't correctly process `!= OR` queries.
Fixed internal issue ES-544: Instantiation of AQL queries with graph traversals in a OneShard setting failed with 'direction can only be INBOUND, OUTBOUND or ANY'.
Fixed a rare race condition in SmartGraphs where the graph is unbalanced, but a successful result could be found by only on database server, where the other server is still searching. In this race the query could continue on the other server and hit a non-thread save object.
Fixed a bug in the agency supervision, which ignored the `failoverCandidates` field.
AQL bugfix for the OneShard database optimizer rule when working with both OneShard collections and satellite collections. Previously, queries could not be instantiated unless the leader of the satellite collection was, by chance, on the same server.
Now the OneShard feature does allow reading from satellite collections, while queries writing to a satellite collection will no longer trigger the OneShard optimization.
Changed behavior for creating new collections in OneShard databases (i.e. databases with "sharding" attribute set to "single"):
Previously it was allowed to override "distributeShardsLike" and "numberOfShards" for each new collection. The default values were "_graphs" and 1 and were not modified if the user did not alter them, but it was still possible to alter them.
This is now (silenly) ignored. Any attempt to set any value for "distributeShardsLike" or "numberOfShards" for new collections in a OneShard database will silently be ignored. The collection will automatically be sharded like the sharding prototype and will have a single shard.
The behavior has been adjusted to match the behavior when creating collections in a cluster started with `--cluster.force-one-shard true` option. Here any user-supplied values for "distributeShardsLike" or "numberOfShards" were always ignored.
Now the behavior is identical for OneShard databases and databases in cluster started with `--cluster.force-one-shard true`.
The web interface now also hides the "Distribute shards like" settings in this case, and makes the "Number of shards" input box read-only.
Fixed issue #11275: indexes backward compatibility broken in 3.5+.
Fix an endless loop in FollowerInfo::persistInAgency which could trigger a hanger if a collection was dropped at the wrong time.
Fix cluster representation of the collection figures for RocksDB.
Fix SORT RAND() LIMIT 1 optimization for RocksDB when only a projection of the attributes was used. When a projection was used and that projection was covered by an index (e.g. `_key` via the primary index), then the access pattern was transformed from random order collection seek to an index access, which always resulted in the same index entry to be returned and not a random one.

New in ArangoDB 3.6.2 (Mar 12, 2020)

Legacy behaviour for maintenance mode in supervision.
Fix the usage of the AQL functions `CALL` and `APPLY` for calling user-defined AQL functions when invoking an AQL query from the arangosh or a client application.
Previously, invoking an AQL query and using the `CALL` or `APPLY` AQL functions
to call user-defined AQL function caused undefined behavior.
Fix nullptr deference in index skipping mode, which produced an address sanitizer (ASan) warning.
Fix supervision mode detection while unlocking agency in cluster hot backups.
Clear backups from DB servers and agency, when plan unchanged not met and not allowing for inconsistency.
Fix arangorestore: If a smartGraphAttribute value was changed after document creation, the _key of the document becomes inconsistent with the smartGraphAttribute entry. However, the sharding of documents stays intact. When restoring data from a dump that contains a document with inconsistent _key and smartGraphAttribute this would cause an error and the document would not be inserted. This is fixed by ignoring this inconsistency in the case of restore.
Honor `cacheEnabled` attribute when updating the properties of a collection in case of the cluster. Previously, this attribute was ignored in the cluster, but it shouldn't have been.
Fixed issue #11137: http-proxy can't pass delete method req.body to foxx.
Fixed a memory leak in ModificationExecutors.
Updated rclone to 1.51.1.
Fixed queries having the following structure
FOR doc IN collection
FILTER doc.nonIndexedAttribute // expression
FOR sub IN doc.nonIndexedAttribute // same expression
For such queries, the FILTER was moved into the first FOR loop for early pruning. Afterwards, the leftover CalculationNode that evaluated `doc.nonIndexedAttribute` was removed. This was wrong however, because
the same expression was reused in the second FOR loop. There was code considering this, but due to a bug it did not work if the expression in the FILTER was reused in the directly following node.
Updated arangosync to 0.7.3.
Updated ArangoDB Starter to 0.14.14.
Fixed handling of `geometry` attributes in query editor of the web UI.
Previously, document attributes named `geometry` were treated in a special
way, assuming they were JSON objects. In case a document contained a
`geometry` attribute that had a non-object value (e.g. `null`) the web UI
threw a JavaScript exception and would not display AQL query results properly.
Disable "collect-in-cluster" AQL optimizer rule in case a LIMIT node is between
the COLLECT and the source data. In this case it is not safe to apply the
distributed collect, as it may alter the results.
Fixed internal issue #4932: COLLECT WITH COUNT together with FILTER yields
zero.
This bugfix fixes an issue when skipping over documents in an index scan using a covering index and also at the same time using an early-pruning filter.
In this case wrong document data may have been injected into the filter condition for filtering, with the filter wrongfully deciding which documents to filter out.
Improved usability in arangorestore: Fixed misleading error message when database creation fails for option`--create-database option`. Now the correct error is displayed.
Pass the specified replication factor from the `--replication-factor`option when creating a database.
Fixed issue #11051: AQL query wrongfully returning no results on 3.6.1.
This bugfix prevents the "late-document-materialization" optimizer rule from kicking in in cases when an index scan also uses early pruning of index entries. In this case, the late document materialization will lead to the filter condition used in early pruning not being applied correctly, potentially producing wrong results.
Fixed `console.log(...)` not logging when called inside arangosh.
Curiously, `require("console").log(...)` still worked from arangosh. This bugfix makes both versions work again.
Fixed internal issue #596: Added ability to disable DNF conversion in SEARCH condition for ArangoSearch views. As this conversion might result in overcomplicated disjunction and heavily slowdown execution.
Fixed a bug where a single host agency could log too early.
Cluster collection creation preconditioned on involved db server not in process of being cleaned and beyond.
Supervision maintenance mode from "on" and TTL to expiry string.
Clean out server job checks preconditions plan version unchanged for start.
Make sure heartbeats are actually sent out and received once per second.
Make active failover integration tests more stable.
Include collections "_queues" and "_jobs" in dumps created by arangodump in case the option `--include-system-collections` was set to true. Previously these collections were always excluded from dumps.
Fix bug in collection creation with distributeShardsLike.
Fixed issue #10949: k shortest paths behaviour wrong with zero weights.

New in ArangoDB 3.6.0 (Jan 8, 2020)

New in ArangoDB 3.5.3 (Nov 29, 2019)

Fixed GET _api/gharial to also include the name property in every returned graph. This is a consistency fix within the API as all other APIs include the name. As a work around the returned _key can be used, which is identical to the name.
The _users collection is now properly restored when using arangorestore.
Allow the optimizer to use indexes when a collection attribute is compared to an expansion followed by an attribute name, e.g. `doc.value IN something[*].name`.
Updated arangosync to 0.7.0.
Fixed issue #10470: The WebUI now shows potential errors and details which occured using _api/import (e.g. unique constraint violated).
Fixed issue #10440: Incorrect sorting with sort criteria partially covered by index.
Make the timeouts for replication requests (for active failover and master-slave replication configurable via startup options:
--replication.connect-timeout
--replication.request-timeout
Fixed internal issue #4647: dead Coordinators are not removed for agency.
Fixed UPSERT matching.
This will now correctly insert a document instead of updating the existing, that only partially machtes the upsert-expression.
Fixed undefined behaviour with creation of ArangoSearch links with custom analyzers in cluster environment.
Fixed internal issue #651: analyzer duplication in _analyzers collection.
Fixed internal issue #4597: rebalanceShards API cannot work on any database other than the _system database.
Stop putting system services in _apps on single server, this has never worked on cluster and was not needed.
Fixed issue #10371: K_SHORTEST_PATHS LIMIT 1 can not return the shortest path.
Now the shortest path is returned as the first one in such queries.
Improve killability of some types of cluster AQL queries. Previously, several cluster queries, especially those containing a `DistributeNode` in their execution plans, did not respond to a kill instruction.
This change also introduces a new query status "killed", which may now be returned by the REST APIs at `/_api/query/current` and `/_api/query/slow` in the `state` attribute of each query.
Improve shutdown of some cluster AQL queries on the coordinator in case the query has multiple coordinator snippets (true for queries involving more than one collection) and the database server(s) cannot be reached on query shutdown. In this case the proper shutdown of the coordinator parts of the query previously was deferred until the coordinator snippets were removed by the automatic garbage collection. Now, the cleanup of the coordinator snippets will happen much more quickly, which reduces the chances of the queries blocking resources.
Fixed ArangoSearch index removes being discarded on commiting consolidation results with pending removes after some segments under consolidation were already committed.
Assertion fail when no timestamp in agency's persistence.
Fixed internal issue #647: custom analyzer provokes errors on Active Failover deployment.
Upgraded bundled version of libcurl to 7.66.0.
When starting a coordinator, wait up to 15 seconds for it to appear in the agency under key `Supervision/Health` before reporting as "ready".
This is necessary because if the coordinator reports ready beforehand and is used to create databases etc., the supervision may remove all of the jobs started by non-ready coordinators, considering them to be from a failed coordinator.
To avoid huge startup delays, the startup will proceed after waiting futilely for 15 seconds and log a message.
Fixed issue #10270: Query: Expecting type Array or Object (while executing).
Fix a problem with AQL constrained sort in the cluster, which might abort queries. The AQL sort-limit optimization rule may now also speed up fullCount with sorted indexes and a limit in the cluster.
Prevent spurious log message "Scheduler queue is filled more than 50% in last x s" from occurring when this is not the case. Due to a data race, the message could previously also occur if the queue was empty.
The General Graph document API is now consistent with the document API in its error messages. When attempting to create / modify edges pointing to non existing vertex collections HTTP 400 is returned instead of 404.
Disallow the usage of subqueries inside AQL traversal PRUNE conditions.
Using subqueries inside PRUNE conditions causes undefined behavior, so such queries will now be aborted early on with a parse error instead of running into undefined behavior.
Fixed available flag for hotbackup.
Fixed list with id for partially available hotbackups.
Fixed agency TTL bug happening under certain rare conditions.
Improved performance of some agency helper functions.
Fixed search not working in document view while in code mode.
Fixed issue #10090: fix repeatable seek to the same document in SEARCH operations for ArangoSearch views.
Fixed issue #10193: Arangoexport does not handle line feeds when exporting as csv.
Removed debug log messages "found comm task ..." that could be logged on server shutdown.
Fixed issue #10183: Arangoimport imports on _system when you try to create a new database.
This bugfix fixes the output of arangoimport, which could display a wrong target database for the import if the option `--create-database` was used.
Fixed issue #10158: Invalid Query Crashes ArangoDB.
This fixes traversal queries that are run on a static empty start vertex string.

New in ArangoDB 3.5.0 (Aug 21, 2019)

New in ArangoDB 3.4.7 (Jul 5, 2019)

Updated arangosync to 0.6.4
Bug-fix for a very rare race condition on cluster collection creation process.
Fixed internal issue #4040: gharial api is now checking existence of `_from` and `_to` vertices during edge replacements and edge updates
Fix timeout-response in case of simultaneous index create/drop in cluster
Fixed editing a user within the web UI if the user added a gravatar profile picture
Fixed internal issue #4172: on agent servers the RocksDB WAL files in the archive directory were retained due to an error. Now they are removed, eventually
Fix error reporting in arangorestore. previously, when the server returned an HTTP 404 error, arangorestore unconditionally translated this into a "collection not found" error, which may have masked an actually different server-side error. Instead, make arangorestore return the server's actual error message as is.
Allow pregel to select the shard key via `shardKeyAttribute` in pregel start parameters
Speed up collection creation process in cluster, if not all agency callbacks are delivered successfully.
Fixed parsing of ArangoDB config files with inlined comments. Previous versions didn't handle line comments properly if they were appended to an otherwise valid option value.
This version fixes the handling of comments in the config files so that they behave as intended.
Fixed AQL query tracing for traversals, this lead to wrong "calls" count in query profiles
Pregel algorithms can be run with the option "useMemoryMaps: true" to be able to run algorithms on data that is bigger than the available RAM.
Bugfix for smart graph traversals with uniqueVertices: path, which could sometimes lead to erroneous traversal results
The system-collection '_jobs' will from now on use non-unique, non-sparse indexes.
Fixed internal issue #3919: The web UI is now using precompiled ejs templates.
Properly create VERSION files for any newly created databases again, as it has been the case in 3.3 and before. If no VERSION files are created, this may cause problems on upgrade to 3.5. The 3.5 branch was also modified to handle this problem gracefully.
Fixed "collection not found" exception during setup of 3-way smart join queries in the cluster
Fixed an edge case of handling `null` values in the AQL function `MIN` for input sequences that started with a `null` value. In this case, `null` was always returned as the minimum value even though other non-null values may have followed, and `MIN` was supposed to return `null` only if there are no input values or all input values are `null`.
Fix client id lookup table in agency
Fix agency's handling of object assignments with TTL
Reduce resident memory usage when creating non-unique indexes with the RocksDB storage engine
Fix agency election bug.

New in ArangoDB 3.4.6.1 (Jun 7, 2019)

New in ArangoDB 3.4.6 (May 29, 2019)

updated ArangoDB Starter 0.14.4
Fixed internal issue #3912: improved the performance of graph creation with multiple relations. They do now create multiple collections within a single round-trip in the agency.
Fixed a crash when posting an async request to the server using the "x-arango-async" request header and the server's request queue was full
Added error code 1240 "incomplete read" for RocksDB-based reads which cannot retrieve documents due to the RocksDB block cache being size-restricted (with size limit enforced) and uncompressed data blocks not fitting into the block cache
The error can only occur for collection or index scans with the RocksDB storage engine when the RocksDB block cache is used and set to a very small size, plus its maximum size is enforced by setting the `--rocksdb.enforce-block-cache-size-limit` option to `true`.
Previously these incomplete reads could have been ignored silently, making collection or index scans return less documents than there were actually present.
Fixed internal issue #3918: added optional second parameter "withId" to AQL function PREGEL_RESULT this parameter defaults to `false`. When set to `true` the results of the Pregel
computation run will also contain the `_id` attribute for each vertex and not just `_key`. This allows distinguishing vertices from different vertex collections.
Fixed issue #7011: description when replacing a foxx application was misleading
Fixed issue #8841: Graph Viewer dropped ability to edit an edge after rerendering.
Upgraded arangodb starter version to 0.14.3
Fix removal of sort order for sorted results that were passed into a RETURN DISTINCT in an AQL query running on a collection with more than a single shard. In this case, the results from the individual shards were sorted, but the overall result was not sorted according to the sort criterion.
Removed bug during start up with a single agent, that leads to dbserver crash.
Fix the creation of debug packages (in the web interface) for queries that involve smart graphs and/or multiple edge collections from a traversal
Add --compress-output flag to arangodump. Activates gzip compression for collection data. Metadata files, such as .structure.json and .view.json, do not get compressed. No option is needed for arangorestore to restore
.data.json.gz files.
Fixed internal issue #3893: correct wrong option name `--database.ignore-logfile-errors` in error message and correct it to `--database.ignore-datafile-errors`
Fixed internal issue #2946: create graph autocomplete was not working under certain circumstances.
Fixed a memory leak in PRUNE operation for traversals.
The leak occurred only when PRUNE was actively used in queries.
Fixed a crash (SIGSEGV) when opening a RocksDB database directory that contained an empty (0 bytes filesize) journal file and encryption was in use.
Improve test performance by doing the 0.1 delay between phase 1 and 2 only if phase 1 is slow
Port back timestamp replication in agency from devel
Better logging when scheduler queue is half-full and full
Fixed internal issue #536: ArangoSearch query may crash during internal lookup in some cases due to invalid index structure for exact input data

New in ArangoDB 3.4.5 (Apr 9, 2019)

Fixed a shutdown issue when the server was shut down while there were active Pregel jobs executing
Fixed internal issue #3815: fixed the removal of connected edges when removing a vertex graph node in a smart graph environment.
Added AQL functions CRC32 and FNV64 for hashing data
Internal issue #2276: fixed the sorting of the databases in the database selection dropdown in the web ui. The sort order differed based on whether authentication was enabled or disabled.
Fixed internal issue #3789: restricted the allowed query names for user-defined custom queries within the web ui.
Fixed internal issuel #3546: improved the shards view in the web ui if there is only one shard to display.
Fixed a display issues when editing a graph within the web ui
Fixed internal-issue #3787: Let user know about conflicting attribute in AQL queries if information is available.
Fixed issue #8294: wrong equals behaviour on arrays with ArangoSearch
Fixed internal issue #528: ArangoSearch range query sometimes doesn't work correctly with numeric values
Fixed internal issue #3757: when restarting a follower in active failover mode, try an incremental sync instead of a full resync. Fixed also the case where a double resync was made
Don't check for the presence of ArangoDB upgrades available when firing up an arangosh enterprise edition build
Added startup option `--rocksdb.allow-fallocate`
When set to true, allows RocksDB to use the fallocate call. If false, fallocate calls are bypassed and no preallocation is done. Preallocation is turned on by default, but can be turned off for operating system versions that are known to have issues with it. This option only has an effect on operating systems that support fallocate.
Added startup option `--rocksdb.limit-open-files-at-startup`
If set to true, this will limit the amount of .sst files RocksDB will inspect at startup, which can reduce the number of IO operations performed at start.
Don't run compact() on a collection after a truncate() was done in the same transaction
running compact() in the same transaction will only increase the data size on disk due to RocksDB not being able to remove any documents physically due to the snapshot that is taken at transaction start.
This change also exposes db..compact() in the arangosh, in order to manually run a compaction on the data range of a collection should it be needed for maintenance.
Don't attempt to remove non-existing WAL files, because such attempt will trigger unnecessary error log messages in the RocksDB library
Updated arangosync to 0.6.3
Added --log.file-mode to specify a file mode of newly created log files
Added --log.file-group to specify the group of newly created log files
Fixed some escaping issues within the web ui.
Fixed issue #8359: How to update a document with unique index (constraints)?
When restarting a follower in active failover mode, try an incremental sync instead of a full resync
Add "PRUNE " to AQL Traversals (internal issue #3068). This allows to early abort searching of unnecessary branches within a traversal. PRUNE is only allowed in the Traversal statement and only between the graphdefinition and the options of the traversal.
Added option `--console.history` to arangosh for controlling whether the command-line history should be loaded from and persisted in a file.
The default value for this option is `true`. Setting it to `false` will make arangosh not load any command-line history from the history file, and not store the current session's history when the shell is exited. The command-line history will then only be available in the current shell session.
Display the server role when connecting arangosh against a server (e.g. SINGLE, COORDINATOR)
Added replication applier state figures `totalDocuments` and `totalRemovals` to access the number of document insert/replace operations and the number of document removals operations separately. Also added figures `totalApplyTime` and `totalFetchTime` for determining the total time the replication spent for applying changes or fetching new data from the master. Also added are the figures `averageApplyTime` and `averageFetchTime`, which show the average time spent for applying a batch or for fetching data from the master, resp.
Fixed race condition in which the value of the informational replication applier figure `ticksBehind` could underflow and thus show a very huge number of ticks.
Always clear all ongoing replication transactions on the slave if the slave discovers the data it has asked for is not present anymore on the master and the `requireFromPresent` value for the applier is set to `false`.
In this case aborting the ongoing transactions on the slave is necessary because they may have held exclusive locks on collections, which may otherwise not be released.
Added option `--rocksdb.wal-archive-size-limit` for controlling the maximum total size (in bytes) of archived WAL files. The default is 0 (meaning: unlimited).
When setting the value to a size bigger than 0, the RocksDB storage engine will force a removal of archived WAL files if the total size of the archive exceeds the configured size. The option can be used to get rid of archived WAL files in a disk size-constrained environment. Note that archived WAL files are normally deleted automatically after a short while when there is no follower attached that may read from the archive. However, in case when there are followers attached that may read from the archive, WAL files normally remain in the archive until their contents have been streamed to the followers. In case there are slow followers that cannot catch up this will cause a growth of the WAL files archive over time. The option `--rocksdb.wal-archive-size-limit` can now be used to force a deletion of WAL files from the archive even if there are followers attached that may want to read the archive. In case the option is set and a leader deletes files from the archive that followers want to read, this will abort the replication on the followers. Followers can however restart the replication doing a resync.
Agents need to be able to overwrite a compacted state with same _key
In case of resigned leader, set isReady=false in clusterInventory
Abort RemoveFollower job if not enough in-sync followers or leader failure
Fix shrinkCluster for satelliteCollections
Fix crash in agency supervision when leadership is lost
Speed up supervision in agency for large numbers of jobs
Fix log spamming after leader resignation in agency
Make AddFollower less aggressive
Fix cases, where invalid json could be generated in agents' store dumps
Coordinator route for full agency dumps contains compactions and time stamps
Lots of agency performance improvements, mostly avoiding copying
Priority queue for maintenance jobs
Do not wait for replication after each job execution in Supervision
Fix a blockage in MoveShard if a failover happens during the operation
Check health of servers in Current before scheduling removeFollower jobs
Wait for statistics collections to be created before running resilience tests
Fix ttl values in agency when key overwritten with no ttl

New in ArangoDB 3.4.4 (Apr 8, 2019)

New in ArangoDB 3.3.14 (Sep 1, 2018)

New in ArangoDB 3.3.11 (Jul 5, 2018)

New in ArangoDB 3.3 Milestone 2 (Oct 24, 2017)

New in ArangoDB 3.2.4 (Sep 27, 2017)

New in ArangoDB 3.2.3 (Sep 11, 2017)

New in ArangoDB 3.2.2 (Sep 6, 2017)

New in ArangoDB 3.2.1 (Aug 11, 2017)

Fixed issue #3011: 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.
fixed an isse with restoring of system collections and user rights. It was not possible to restore users into an authenticated server.
fixed issue #2977: Documentation for db._createDatabase is wrong
ui: added bind parameters to slow query history view
fixed issue #1751: Slow Query API should provide bind parameters, webui should display them
ui: fixed a bug when moving multiple documents was not possible
fixed docs for issue #2968: 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
fixed a multi-threading issue in the agency when callElection was called while the Supervision was calling updateSnapshot
added startup option `--query.tracking-with-bindvars`
index selectivity estimates are now available in the cluster as well
fixed issue #2943: loadIndexesIntoMemory not returning the same structure as the rest of the collection APIs
fixed issue #2949: ArangoError 1208: illegal name
fixed issue #2874: Collection properties do not return `isVolatile` attribute
potential fix for issue #2939: Segmentation fault when starting coordinator node
fixed issue #2810: out of memory error when running UPDATE/REPLACE on medium-size collection
fix potential deadlock errors in collector thread
disallow the usage of volatile collections in the RocksDB engine by throwing an error when a collection is created with attribute `isVolatile` set to `true`. Volatile collections are unsupported by the RocksDB engine, so creating them should not succeed and silently create a non-volatile collection
prevent V8 from issuing SIGILL instructions when it runs out of memory
Foxx queues and tasks now ensure that the scripts in them run with the same permissions as the Foxx code who started the task / queue
fixed issue #2928: Offset problems
fixed issue #2876: wrong skiplist index usage in edge collection
fixed issue #2868: cname missing from logger-follow results in rocksdb
fixed issue #2889: Traversal query using incorrect collection id
fixed issue #2884: AQL traversal uniqueness constraints "propagating" to other traversals? Weird results
arangoexport: added `--query` option for passing an AQL query to export the result
fixed issue #2879: No result when querying for the last record of a query
ui: allows now to edit default access level for collections in database _system for all users except the root user.
added new option "--rocksdb.max-background-jobs"
removed options "--rocksdb.max-background-compactions", "--rocksdb.base-background-compactions" and "--rocksdb.max-background-flushes"
option "--rocksdb.compaction-read-ahead-size" now defaults to 2MB
change Windows build so that RocksDB doesn't enforce AVX optimizations by default
speed up RocksDB secondary index creation and dropping
removed RocksDB note in Geo index docs

New in ArangoDB 3.2.0 (Aug 3, 2017)

New in ArangoDB 3.1.26 (Jul 28, 2017)

New in ArangoDB 3.1.25 (Jul 15, 2017)

New in ArangoDB 3.1.24 (Jul 15, 2017)

New in ArangoDB 3.1.23 (Jul 3, 2017)

New in ArangoDB 3.1.11 (Feb 21, 2017)

New in ArangoDB 3.1.9 (Feb 20, 2017)

New in ArangoDB 3.0.12 (Nov 26, 2016)

New in ArangoDB 3.0.10 (Sep 27, 2016)

New in ArangoDB 3.0.8 (Sep 16, 2016)

New in ArangoDB 3.0.7 (Sep 7, 2016)

New in ArangoDB 3.0.6 (Sep 5, 2016)

New in ArangoDB 3.0.5 (Sep 2, 2016)

New in ArangoDB 3.0.3 (Jul 17, 2016)

New in ArangoDB 3.0.2 (Jul 10, 2016)

New in ArangoDB 3.0.1 (Jul 1, 2016)

New in ArangoDB 2.8.9 (Jun 23, 2016)

New in ArangoDB 3.0.0 RC 3 (Jun 23, 2016)

New in ArangoDB 2.8.7 (Apr 8, 2016)

New in ArangoDB 2.8.6 (Mar 25, 2016)

New in ArangoDB 2.8.5 (Mar 12, 2016)

New in ArangoDB 2.8.4 (Mar 2, 2016)

New in ArangoDB 2.8.3 (Feb 25, 2016)

New in ArangoDB 2.8.2 (Feb 10, 2016)

New in ArangoDB 2.8.1 (Jan 31, 2016)

New in ArangoDB 2.8.0 (Jan 28, 2016)

New in ArangoDB 2.7.3 (Dec 21, 2015)

New in ArangoDB 2.7.0 (Oct 25, 2015)

New in ArangoDB 2.6.5 (Aug 19, 2015)

New in ArangoDB 2.6.4 (Aug 15, 2015)

New in ArangoDB 2.6.2 (Jul 6, 2015)

New in ArangoDB 2.5.5 (Jun 2, 2015)

New in ArangoDB 2.5.4 (May 18, 2015)

New in ArangoDB 2.5.3 (May 6, 2015)

New in ArangoDB 2.5.2 (Apr 16, 2015)

New in ArangoDB 2.5.1 (Mar 23, 2015)

New in ArangoDB 2.5.0 (Mar 17, 2015)

New in ArangoDB 2.4.4 (Mar 2, 2015)

New in ArangoDB 2.4.3 (Feb 9, 2015)

New in ArangoDB 2.4.2 (Feb 4, 2015)

New in ArangoDB 2.4.1 (Jan 21, 2015)

New in ArangoDB 2.4.0 (Jan 19, 2015)

New in ArangoDB 2.3.4 (Jan 17, 2015)

New in ArangoDB 2.3.3 (Dec 18, 2014)

New in ArangoDB 2.3.2 (Dec 11, 2014)

New in ArangoDB 2.3.1 (Dec 11, 2014)

New in ArangoDB 2.3.0 (Nov 26, 2014)

New in ArangoDB 2.2.6 (Oct 22, 2014)

New in ArangoDB 2.2.5 (Oct 13, 2014)

New in ArangoDB 2.2.4 (Oct 3, 2014)

New in ArangoDB 2.2.3 (Sep 4, 2014)

New in ArangoDB 2.2.2 (Aug 9, 2014)

New in ArangoDB 2.2.1 (Jul 25, 2014)

New in ArangoDB 2.2.0 (Jul 14, 2014)

The replication methods `logger.start`, `logger.stop` and `logger.properties` are no-ops in ArangoDB 2.2 as there is no separate replication logger anymore. Data changes are logged into the write-ahead log in ArangoDB 2.2, and not separately by the replication logger. The replication logger object is still there in ArangoDB 2.2 to ensure backwards-compatibility, however, logging cannot be started, stopped or configured anymore. INCOMPATIBLE CHANGE: replication of transactions has changed. Previously, transactions were logged on a master in one big block and shipped to a slave in one block, too. Now transactions will be logged and replicated as separate entries, allowing transactions to be bigger and also ensure replication progress. INCOMPATIBLE CHANGE: the figures reported by the `collection.figures` method now only reflect documents and data contained in the journals and datafiles of collections. Documents or deletions contained only in the write-ahead log will not influence collection figures until the write-ahead log garbage collection kicks in. The figures for a collection might therefore underreport the total resource usage of a collection. Additionally, the attributes `lastTick` and `uncollectedLogfileEntries` have been added to the result of the `figures` operation and the HTTP API method `PUT /_api/collection/figures`
added `insert` method as an alias for `save`.
added support for data-modification AQL queries
added AQL keywords `INSERT`, `UPDATE`, `REPLACE` and `REMOVE` (and `WITH`) to support data-modification AQL queries. disallow storing of JavaScript objects that contain JavaScript native objects of type `Date`, `Function`, `RegExp` or `External`. The replication methods `logger.start`, `logger.stop` and `logger.properties` are no-ops in ArangoDB 2.2 as there is no separate replication logger anymore. Data changes are logged into the write-ahead log in ArangoDB 2.2, and not separately by the replication logger. The replication logger object is still there in ArangoDB 2.2 to ensure backwards-compatibility, however, logging cannot be started, stopped or configured anymore. Using any of these methods will do nothing. INCOMPATIBLE CHANGE: replication of transactions has changed. Previously, transactions were logged on a master in one big block and shipped to a slave in one block, too. Now transactions will be logged and replicated as separate entries, allowing transactions to be bigger and also ensure replication progress. INCOMPATIBLE CHANGE: the figures reported by the `collection.figures` method now only reflect documents and data contained in the journals and datafiles of collections. Documents or deletions contained only in the write-ahead log will not influence collection figures until the write-ahead log garbage collection kicks in. The figures for a collection might therefore underreport the total resource usage of a collection.
added `insert` method as an alias for `save`.
added support for data-modification AQL queries
added AQL keywords `INSERT`, `UPDATE`, `REPLACE` and `REMOVE` (and `WITH`) to support data-modification AQL queries. disallow storing of JavaScript objects that contain JavaScript native objects of type `Date`, `Function`, `RegExp` or `External`.
honor startup option `--server.disable-statistics` when deciding whether or not to start periodic statistics collection jobs.
removed startup option `--random.no-seed`. This option had no effect in previous versions of ArangoDB and was thus removed.
removed startup option `--database.remove-on-drop`. This option was used for debugging only.
removed startup option `--database.force-sync-properties`. This option is now superfluous as collection properties are now stored in the write-ahead log.
introduced write-ahead log
removed startup option `--server.disable-replication-logger`. This option is superfluous in ArangoDB 2.2. There is no dedicated replication logger in ArangoDB 2.2. There is now always the write-ahead log, and it is also used as the server's replication log. Specifying the startup option `--server.disable-replication-logger` will do nothing in ArangoDB 2.2, but the option should not be used anymore as it might be removed in a future version.
changed behavior of replication logger. There is no dedicated replication logger in ArangoDB 2.2 as there is the write-ahead log now. The existing APIs for starting and stopping the replication logger still exist in ArangoDB 2.2 for downwards-compatibility, but calling the start or stop operations are no-ops in ArangoDB 2.2. When querying the replication logger status via the API, the server will always report that the replication logger is running. Configuring the replication logger is a no-op in ArangoDB 2.2, too. Changing the replication logger configuration has no effect. Instead, the write-ahead log configuration can be changed.
removed MRuby integration for arangod
reclaim index memory when last document in collection is deleted inlined and optimized functions in hash indexes
added AQL TRANSLATE function
fixed datafile debugger
fixed check-version for empty directory
moved try/catch block to the top of routing chain
added mountedApp function for foxx-manager
fixed issue #883: arango 2.1 - when starting multi-machine cluster, UI web does not change to cluster overview
fixed dfdb: should not start any other V8 threads
cleanup of version-check, added module org/arangodb/database-version, added --check-version option
fixed issue #881: [2.1.0] Bombarded (every 10 sec or so) with "WARNING format string is corrupt" when in non-system DB Dashboard
specialized primary index implementation to allow faster hash table rebuilding and reduce lookups in datafiles for the actual value of `_key`.
issue #862: added `--overwrite` option to arangoimp
removed number of property lookups for documents during AQL queries that access documents
prevent buffering of long print results in arangosh's and arangod's print command. removed sorting of attribute names for use in a collection's shaper
fixed a bug in arangodump which got the collection name in _from and _to attributes of edges wrong (all were "_unknown")
fixed a bug in arangorestore which did not recognise wrong _from and _to attributes of edges
improved error detection and reporting in arangorestore

New in ArangoDB 2.1.1 (Jun 9, 2014)

New in ArangoDB 2.1.0 (May 30, 2014)

New in ArangoDB 2.0.7 (May 6, 2014)

New in ArangoDB 2.0.6 (Apr 24, 2014)

New in ArangoDB 2.0.5 (Apr 24, 2014)

New in ArangoDB 2.0.4 (Apr 15, 2014)

New in ArangoDB 2.0.3 (Apr 14, 2014)

New in ArangoDB 2.0.2 (Apr 7, 2014)

New in ArangoDB 2.0.1 (Apr 2, 2014)

New in ArangoDB 2.0.0 RC 2 (Mar 12, 2014)

New in ArangoDB 2.0.0 RC1 (Mar 4, 2014)

added sharding - more detailed documentation on the sharding and cluster features can be found in the user manual, section **Sharding**
INCOMPATIBLE CHANGE: using complex values in AQL filter conditions with operators other than equality will disable usage of skiplist indexes for filter evaluation. For example, the following queries will be affected by change:
FOR doc IN docs FILTER doc.value < { foo: "bar" } RETURN doc FOR doc IN docs FILTER doc.value >= [ 1, 2, 3 ] RETURN doc
The following queries will not be affected by the change: FOR doc IN docs FILTER doc.value == 1 RETURN doc FOR doc IN docs FILTER doc.value == "foo" RETURN doc FOR doc IN docs FILTER doc.value == [ 1, 2, 3 ] RETURN doc FOR doc IN docs FILTER doc.value == { foo: "bar" } RETURN doc
INCOMPATIBLE CHANGE: removed undocumented method `collection.saveOrReplace` this feature was never advertised nor documented nor tested.
INCOMPATIBLE CHANGE: removed undocumented REST API method `/_api/simple/BY-EXAMPLE-HASH` this feature was never advertised nor documented nor tested.
added explicit startup parameter `--server.reuse-address`. This flag can be used to control whether sockets should be acquired with the SO_REUSEADDR flag. Regardless of this setting, sockets on Windows are always acquired using the SO_EXCLUSIVEADDRUSE flag.
removed undocumented REST API method GET `/_admin/database-name`
added user validation API at POST `/_api/user/`
slightly improved users management API in `/_api/user`:
Previously, when creating a new user via HTTP POST, the username needed to be passed in an attribute `username`. When users were returned via this API, the usernames were returned in an attribute named `user`. This was slightly confusing and was changed in 1.5 as follows:
when adding a user via HTTP POST, the username can be specified in an attribute `user`. If this attribute is not used, the API will look into the attribute `username` as before and use that value. - when users are returned via HTTP GET, the usernames are still returned in an attribute `user`.
This change should be fully downwards-compatible with the previous version of the API.
added AQL SLICE function to extract slices from lists
removed check-server binary
made module loader more node compatible
the startup option `--javascript.package-path` for arangosh is now deprecated and does nothing. Using it will not cause an error, but the option is ignored.
added coffee script support
Several UI improvements.
Exchanged icons in the graphviewer toolbar
always start networking and HTTP listeners when starting the server (even in console mode)
allow vertex and edge filtering with user-defined functions in TRAVERSAL, TRAVERSAL_TREE and SHORTEST_PATH AQL functions:
// using user-defined AQL functions for edge and vertex filtering RETURN TRAVERSAL(friends, friendrelations, "friends/john", "outbound", { followEdges: "myfunctions::checkedge", filterVertices: "myfunctions::checkvertex" })
// using the following custom filter functions var aqlfunctions = require("org/arangodb/aql/functions"); aqlfunctions.register("myfunctions::checkedge", function (config, vertex, edge, path) { return (edge.type !== 'dislikes'); // don't follow these edges }, false);
aqlfunctions.register("myfunctions::checkvertex", function (config, vertex, path) { if (vertex.isDeleted || ! vertex.isActive) { return [ "prune", "exclude" ]; // exclude these and don't follow them } return [ ]; // include everything else }, false);
fail if invalid `strategy`, `order` or `itemOrder` attribute values are passed to the AQL TRAVERSAL function. Omitting these attributes is not considered an error, but specifying an invalid value for any of these attributes will make an AQL query fail.
issue #751: Create database through API should return HTTP status code 201
By default, the server now returns HTTP 201 (created) when creating a new database successfully. To keep compatibility with older ArangoDB versions, the startup parameter `--server.default-api-compatibility` can be set to a value of `10400` to indicate API compatibility with ArangoDB 1.4. The compatibility can also be enforced by setting the `X-Arango-Version` HTTP header in a client request to this API on a per-request basis.
allow direct access from the `db` object to collections whose names start with an underscore (e.g. db._users).
Previously, access to such collections via the `db` object was possible from arangosh, but not from arangod (and thus Foxx and actions). The only way to access such collections from these places was via the `db._collection()` workaround.
allow `\n` (as well as `\r\n`) as line terminator in batch requests sent to `/_api/batch` HTTP API.
use `--data-binary` instead of `--data` parameter in generated cURL examples
issue #703: Also show path of logfile for fm.config()
issue #675: Dropping a collection used in "graph" module breaks the graph
added "static" Graph.drop() method for graphs API
fixed issue #695: arangosh server.password error
use pretty-printing in `--console` mode by defaul
added `check-server` binary for testing
simplified ArangoDB startup options:
Some startup options are now superfluous or their usage is simplified. The following options have been changed:
`--javascript.modules-path`: this option has been removed. The modules paths are determined by arangod and arangosh automatically based on the value of `--javascript.startup-directory`.
If the option is set on startup, it is ignored so startup will not abort with an error `unrecognized option`.
`--javascript.action-directory`: this option has been removed. The actions directory is determined by arangod automatically based on the value of `--javascript.startup-directory`.
If the option is set on startup, it is ignored so startup will not abort with an error `unrecognized option`.
`--javascript.package-path`: this option is still available but it is not required anymore to set the standard package paths (e.g. `js/npm`). arangod will automatically use this standard package path regardless of whether it was specified via the options.
It is possible to use this option to add additional package paths to the standard value.
Configuration files included with arangod are adjusted accordingly.
layout of the graphs tab adapted to better fit with the other tabs
database selection is moved to the bottom right corner of the web interface
removed priority queue index type - this feature was never advertised nor documented nor tested.
display internal attributes in document source view of web interface
removed separate shape collections:
When upgrading to ArangoDB 1.5, existing collections will be converted to include shapes and attribute markers in the datafiles instead of using separate files for shapes.
When a collection is converted, existing shapes from the SHAPES directory will be written to a new datafile in the collection directory, and the SHAPES directory will be removed afterwards.
This saves up to 2 MB of memory and disk space for each collection (savings are higher, the less different shapes there are in a collection). Additionally, one less file descriptor per opened collection will be used.
When creating a new collection, the amount of sync calls may be reduced. The same may be true for documents with yet-unknown shapes. This may help performance in these cases.
added AQL functions `NTH` and `POSITION`
added signal handler for arangosh to save last command in more cases
added extra prompt placeholders for arangosh: - `%e`: current endpoint - `%u`: current user
added arangosh option `--javascript.gc-interval` to control amount of garbage collection performed by arangosh
fixed issue #651: Allow addEdge() to take vertex ids in the JS library
removed command-line option `--log.format`- In previous versions, this option did not have an effect for most log messages, so it got removed.
removed C++ logger implementation - Logging inside ArangoDB is now done using the LOG_XXX() macros. The LOGGER_XXX() macros are gone.
added collection status "loading"

New in ArangoDB 1.4.11 (Mar 1, 2014)

New in ArangoDB 1.4.9 (Feb 14, 2014)

New in ArangoDB 1.4.8 (Feb 1, 2014)

New in ArangoDB 1.4.7 (Jan 24, 2014)

New in ArangoDB 1.4.6 (Jan 21, 2014)

New in ArangoDB 1.4.5 (Jan 16, 2014)

New in ArangoDB 1.4.4 (Dec 27, 2013)

uid and gid are now set in the scripts, there is no longer a separate config file for arangod when started from a script
foxx-manager is now an alias for arangosh
arango-dfdb is now an alias for arangod, moved from bin to sbin
changed from readline to linenoise for Windows
added --install-service and --uninstall-service for Windows
removed --daemon and --supervisor for Windows
arangosh and arangod now uses the config-file which maps the binary name, i. e. if you rename arangosh to foxx-manager it will use the config file foxx-manager.conf
fixed lock file for Windows
fixed issue #711, #687: foxx-manager throws internal errors
added `--server.ssl-protocol` option for client tools this allows connecting from arangosh, arangoimp, arangoimp etc. to an ArangoDB server that uses a non-default value for `--server.ssl-protocol`. The default value for the SSL protocol is 4 (TLSv1). If the server is configured to use a different protocol, it was not possible to connect to it with the client tools.
added more detailed request statistics. This adds the number of async-executed HTTP requests plus the number of HTTP requests per individual HTTP method type.
added `--force` option for arangorestore this option allows continuing a restore operation even if the server reports errors in the middle of the restore operation
better error reporting for arangorestore in case the server returned an HTTP error, arangorestore previously reported this error as `internal error` without any details only. Now server-side errors are reported by arangorestore with the server's error message
include more system collections in dumps produced by arangodump previously some system collections were intentionally excluded from dumps, even if the dump was run with `--include-system-collections`. for example, the collections `_aal`, `_modules`, `_routing`, and `_users` were excluded. This makes sense in a replication context but not always in a dump context. When specifying `--include-system-collections`, arangodump will now include the above- mentioned collections in the dump, too. Some other system collections are still excluded even when the dump is run with `--include-system-collections`, for example `_replication` and `_trx`.
fixed issue #701: ArangoStatement undefined in arangosh
fixed typos in configuration files

New in ArangoDB 1.4.3 (Nov 26, 2013)

New in ArangoDB 1.4.2 (Nov 26, 2013)

New in ArangoDB 1.4.1 (Nov 12, 2013)

New in ArangoDB 1.4.0 (Nov 1, 2013)

fixed issue #648: /batch API is missing from Web Interface API Docummentation (Swagger)
fixed issue #647: Icon tooltips missing
fixed issue #646: index creation in web interface
fixed issue #645: Allow jumping from edge to linked vertices
merged PR for issue #643: Some minor corrections and a link to "Downloads"
fixed issue #642: Completion of error handling
fixed issue #639: compiling v1.4 on maverick produces warnings on -Wstrict-null-sentinel
fixed issue #634: Web interface bug: Escape does not always propagate
fixed issue #620: added startup option `--server.default-api-compatibility` This adds the following changes to the ArangoDB server and clients: the server provides a new startup option `--server.default-api-compatibility`. This option can be used to determine the compatibility of (some) server API return values. The value for this parameter is a server version number, calculated as follows: `10000 major + 100 minor` (e.g. `10400` for ArangoDB 1.3). The default value is `10400` (1.4), the minimum allowed value is `10300` (1.3). When setting this option to a value lower than the current server version, the server might respond with old-style results to "old" clients, increasing compatibility with "old" (non-up-to-date) clients.
the server will on each incoming request check for an HTTP header `x-arango-version`. Clients can optionally set this header to the API version number they support. For example, if a client sends the HTTP header`x-arango-version: 10300`, the server will pick this up and might send ArangoDB1.3-style responses in some situations.
Setting either the startup parameter or using the HTTP header (or both) allows running "old" clients with newer versions of ArangoDB, without having to adjust the clients too much.
the `location` headers returned by the server for the APIs `/_api/document/...` and `/_api/collection/...` will have different values depending on the used API version. If the API compatibility is `10300`, the `location` headers returned will look like this: location: /_api/document/.... whereas when an API compatibility of `10400` or higher is used, the `location` headers will look like this: location: /_db//_api/document/... Please note that even in the presence of this, old API versions still may not be supported forever by the server.
fixed issue #643: Some minor corrections and a link to "Downloads" by @frankmayer
started issue #642: Completion of error handling
fixed issue #639: compiling v1.4 on maverick produces warnings on -Wstrict-null-sentinel
fixed issue #621: Standard Config needs to be fixed
added function to manage indexes (web interface)
improved server shutdown time by signalling shutdown to applicationserver, logging, cleanup and compactor threads
added foxx-manager `replace` command
added foxx-manager `installed` command (a more intuitive alias for `list`)
fixed issue #617: Swagger API is missing '/_api/version'
fixed issue #615: Swagger API: Some commands have no parameter entry forms
fixed issue #614: API : Typo in : Request URL /_api/database/current
fixed issue #609: Graph viz tool - different background color
fixed issue #608: arangosh config files - eventually missing in the manual
fixed issue #607: Admin interface: no core documentation
fixed issue #603: Aardvark Foxx App Manager
fixed a bug in type-mapping between AQL user functions and the AQL layer.
create less system collections when creating a new database

New in ArangoDB 1.4.0 Alpha 2 (Sep 11, 2013)

New in ArangoDB 1.3.3 (Aug 29, 2013)

New in ArangoDB 1.4.0 Alpha 1 (Aug 5, 2013)

New in ArangoDB 1.3.2 (Aug 5, 2013)

New in ArangoDB 1.3.2 (Jun 22, 2013)

New in ArangoDB 1.3.1 (May 25, 2013)

New in ArangoDB 1.3.0 (May 11, 2013)

New in ArangoDB 1.3.0 RC 1 (Apr 25, 2013)

New in ArangoDB 1.3.0 Alpha 2 (Apr 15, 2013)

New in ArangoDB 1.2.2 (Apr 13, 2013)

New in ArangoDB 1.3 Alpha 1 (Apr 6, 2013)

cleanup of Module, Package, ArangoApp and modules "internal", "fs", "console"
use Error instead of string in throw to allow stack-trace
issue #454: error while creation of Collection
make `collection.count()` not recalculate the number of documents on the fly, but use some internal document counters. This will work at least for non-transactional collections.
issue #457: invalid string value in web interface
make datafile id (datafile->_fid) identical to the numeric part of the filename. E.g. the datafile `journal-123456.db` will now have a datafile marker with the same fid (i.e. `123456`) instead of a different value. This change will only affect datafiles that are created with 1.3 and not any older files. The intention behind this change is to make datafile debugging easier.
consistently discard document attributes with reserved names (system attributes) but without any known meaning, for example `_test`, `_foo`, ... Previously, these attributes were saved with the document regularly in some cases, but were discarded in other cases. Now these attributes are discarded consistently. "Real" system attributes such as `_key`, `_from`, `_to` are not affected and will work as before. Additionally, attributes with an empty name (``) are discarded when documents are saved. Though using reserved or empty attribute names in documents was not really and consistently supported in previous versions of ArangoDB, this change might cause an incompatibility for clients that rely on this feature.
added server startup flag `--database.force-sync-properties` to force syncing of collection properties on collection creation, deletion and on property update. The default value is true to mimic the behavior of previous versions of ArangoDB. If set to false, collection properties are written to disk but no call to sync() is made.
added detailed output of server version and components for REST APIs `/_admin/version` and `/_api/version`. To retrieve this extended information, call the REST APIs with URL parameter `details=true`.
issue #443: For git-based builds include commit hash in version
adjust startup log output to be more compact, less verbose
set the required minimum number of file descriptors to 256. On server start, this number is enforced on systems that have rlimit. If the limit cannot be enforced, starting the server will fail. Note: 256 is considered to be the absolute minimum value. Depending on the use case for ArangoDB, a much higher number of file descriptors should be used. To avoid checking & potentially changing the number of maximum open files, use the startup option `--server.descriptors-minimum 0`
fixed shapedjson to json conversion for special numeric values (NaN, +inf, -inf). Before, "NaN", "inf", or "-inf" were written into the JSONified output, but these values are not allowed in JSON. Now, "null" is written to the JSONified output as required.
added AQL functions VARIANCE_POPULATION(), VARIANCE_SAMPLE(), STDDEV_POPULATION(), STDDEV_SAMPLE(), AVERAGE(), MEDIAN() to calculate stastical values for lists
added AQL SQRT() function
added AQL TRIM(), LEFT() and RIGHT() string functions
fixed issue #436: GET /_api/document on edge make AQL REVERSE() and LENGTH() functions work on strings, too
disabled DOT generation in `make doxygen`. this speeds up docs generation
renamed startup option `--dispatcher.report-intervall` to `--dispatcher.report-interval`
renamed startup option `--scheduler.report-intervall` to `--scheduler.report-interval`
slightly changed output of REST API method /_admin/log. Previously, the log messages returned also contained the date and log level, now they will only contain the log message, and no date and log level information. This information can be re-created by API users from the `timestamp` and `level` attributes of the result.
removed configure option `--enable-zone-debug` memory zone debugging is now automatically turned on when compiling with ArangoDB `--enable-maintainer-mode`
removed configure option `--enable-arangob` arangob is now always included in the build

New in ArangoDB 1.2.1 (Mar 16, 2013)

New in ArangoDB 1.2.0 (Mar 2, 2013)

New in ArangoDB 1.1.2 (Mar 1, 2013)

New in ArangoDB 1.0.0 (Sep 26, 2012)