ArangoDB v3.3.11 Release Notes
Release Date: 2018-06-26 // almost 6 years ago-
⬆️ upgraded arangosync version to 0.5.3
⬆️ upgraded arangodb starter version to 0.12.0
🛠 fixed internal issue #2559: "unexpected document key" error when custom shard keys are used and the "allowUserKeys" key generator option is set to false
🛠 fixed AQL DOCUMENT lookup function for documents for sharded collections with more than a single shard and using a custom shard key (i.e. some shard key attribute other than
_key
). The previous implementation of DOCUMENT restricted to lookup to a single shard in all cases, though this restriction was invalid. That lead toDOCUMENT
not finding documents in cases the wrong shard was contacted. The fixed implementation in 3.3.11 will reach out to all shards to find the document, meaning it will produce the correct result, but will cause more cluster-internal traffic. This increase in traffic may be high if the number of shards is also high, because each invocation ofDOCUMENT
will have to contact all shards. There will be no performance difference for non-sharded collections or collections that are sharded by_key
or that only have a single shard.💻 reimplemented replication view in web UI
🛠 fixed internal issue #2256: ui, document id not showing up when deleting a document
🛠 fixed internal issue #2163: wrong labels within foxx validation of service input parameters
🛠 fixed internal issue #2160: fixed misplaced tooltips in indices view
➕ added new arangoinspect client tool, to help users and customers easily collect information of any ArangoDB server setup, and facilitate troubleshooting for the ArangoDB Support Team