« Changelog History


ArangoDB v3.3.7 Release Notes

Release Date: 2018-04-11 // about 6 years ago

    • ➕ added hidden option --query.registry-ttl to control the lifetime of cluster AQL query parts

    • 🛠 fixed internal issue #2237: AQL queries on collections with replicationFactor: "satellite" crashed arangod in single server mode

    • 🛠 fixed restore of SatelliteCollections: replicationFactor was set to 1 during restore

    • 🛠 fixed dump and restore of SmartGraphs: a) The dump will not include the hidden shadow collections anymore, they were dumped accidentially and only contain duplicated data. b) Restore will now ignore hidden shadow collections as all data is contained in the smart-edge collection. You can manually include these collections from an old dump (3.3.5 or earlier) by using --force. c) Restore of a smart-graph will now create smart collections properly instead of getting into TIMEOUT_IN_CLUSTER_OPERATION

    • 🛠 fixed issue in AQL query optimizer rule "restrict-to-single-shard", which may have sent documents to a wrong shard in AQL INSERT queries that specified the value for _key using an expression (and not a constant value) Important: if you were affected by this bug in v3.3.5 it is required that you recreate your dataset in v3.3.6 (i.e. dumping and restoring) instead of doing a simple binary upgrade

    • ➕ added /_admin/status HTTP API for debugging purposes

    • ➕ added ArangoShell helper function for packaging all information about an AQL query so it can be run and analyzed elsewhere:

    query = "FOR doc IN mycollection FILTER doc.value > 42 RETURN doc"; require("@arangodb/aql/explainer").debugDump("/tmp/query-debug-info", query);

    Entitled users can send the generated file to the ArangoDB support to facilitate reproduction and debugging.

    • ➕ added hidden option --server.ask-jwt-secret. This is an internal option for debugging and should not be exposed to end-users.

    • 🛠 fix for internal issue #2215. supervision will now wait for agent to fully prepare before adding 10 second grace period after leadership change

    • 🛠 fixed internal issue #2215's FailedLeader timeout bug