Known Issues in ArangoDB 3.6

This page lists important issues affecting the 3.6.x versions of the ArangoDB suite of products. It is not a list of all open issues.

Critical issues (ArangoDB Technical & Security Alerts) are also found at arangodb.com/alerts.

ArangoSearch

Issue
Date Added: 2018-12-19
Component: ArangoSearch
Deployment Mode: Single-server
Description: Value of _id attribute indexed by ArangoSearch view may become inconsistent after renaming a collection
Affected Versions: 3.5.x, 3.6.x
Fixed in Versions: -
Reference: arangodb/backlog#514 (internal)
Date Added: 2018-12-03
Component: ArangoSearch
Deployment Mode: Cluster
Description: Score values evaluated by corresponding score functions (BM25/TFIDF) may differ in single-server and cluster with a collection having more than 1 shard
Affected Versions: 3.4.x, 3.5.x, 3.6.x
Fixed in Versions: -
Reference: arangodb/backlog#508 (internal)
Date Added: 2018-12-03
Component: ArangoSearch
Deployment Mode: All
Description: Using a loop variable in expressions within a corresponding SEARCH condition is not supported
Affected Versions: 3.4.x, 3.5.x, 3.6.x
Fixed in Versions: -
Reference: arangodb/backlog#318 (internal)
Date Added: 2019-06-25
Component: ArangoSearch
Deployment Mode: All
Description: The primarySort attribute in ArangoSearch View definitions can not be set via the web interface. The option is immutable, but the web interface does not allow to set any View properties upfront (it creates a View with default parameters before the user has a chance to configure it).
Affected Versions: 3.5.x, 3.6.x
Fixed in Versions: -
Reference: N/A

AQL

Issue
Date Added: 2018-09-05
Component: AQL
Deployment Mode: Cluster
Description: In a very uncommon edge case there is an issue with an optimization rule in the cluster. If you are running a cluster and use a custom shard key on a collection (default is _key) and you provide a wrong shard key in a modifying query (UPDATE, REPLACE, DELETE) and the wrong shard key is on a different shard than the correct one, a DOCUMENT NOT FOUND error is returned instead of a modification (example query: UPDATE { _key: "123", shardKey: "wrongKey"} WITH { foo: "bar" } IN mycollection). Note that the modification always happens if the rule is switched off, so the suggested workaround is to deactivate the optimizing rule restrict-to-single-shard.
Affected Versions: 3.4.x, 3.5.x, 3.6.x
Fixed in Versions: -
Reference: arangodb/arangodb#6399
Date Added: 2020-01-07
Component: AQL
Deployment Mode: Cluster
Description: It is not possible to execute AQL traversals in a cluster using collection sets (anonymous graph) for datasets where edges point to other edges. This is an uncommon use case, but it worked in previous versions.
Affected Versions: 3.6.0
Fixed in Versions: 3.6.1
Reference: arangodb/arangodb#10801

Upgrading

Issue
Date Added: 2019-05-16
Component: arangod
Deployment Mode: All
Description: Bugfix release upgrades such as 3.4.4 to 3.4.5 may not create a backup of the database directory even if they should. Please create a copy manually before upgrading.
Affected Versions: 3.4.x, 3.5.x, 3.6.x (Windows and Linux)
Fixed in Versions: -
Reference: arangodb/planning#3745 (internal)
Date Added: 2019-12-10
Component: Installer
Deployment Mode: All
Description: The NSIS installer for Windows may fail to upgrade an existing installation, e.g. from 3.4.a to 3.4.b (patch release), with the error message: “failed to detect whether we need to Upgrade”
Affected Versions: 3.4.x, 3.5.x, 3.6.x
Fixed in Versions: -
Reference: arangodb/release-qa#183 (internal)
Date Added: 2020-01-07
Component: Installer
Deployment Mode: All
Description: The NSIS installer for Windows can fail to add the path to the ArangoDB binaries to the PATH environment variable, silently or with an error.
Affected Versions: 3.4.x, 3.5.x, 3.6.x
Fixed in Versions: -
Reference: arangodb/release-qa#183 (internal)

Hot Backup

Issue
Date Added: 2019-10-09
Component: Hot Backup API / arangobackup
Deployment Mode: All
Description: The Hot Backup feature is not supported in the Windows version of ArangoDB at this point in time.
Affected Versions: 3.5.x, 3.6.x
Fixed in Versions: -
Reference: N/A
Date Added: 2019-10-09
Component: Hot Backup API / arangobackup
Deployment Mode: DC2DC
Description: Hot Backup functionality in Datacenter to Datacenter Replication setups is experimental and may not work.
Affected Versions: 3.5.x, 3.6.x
Fixed in Versions: -
Reference: N/A
Date Added: 2019-10-09
Component: arangobackup
Deployment Mode: All
Description: The startup option --operation works as positional argument only, e.g. arangobackup list. The alternative syntax arangobackup --operation list is not accepted.
Affected Versions: 3.5.x, 3.6.x
Fixed in Versions: -
Reference: N/A

Other

Issue
Date Added: 2019-05-16
Component: Starter
Deployment Mode: All
Description: The ArangoDB Starter falls back to the IP [::1] under macOS. If there is no entry ::1 localhost in the /etc/hosts file or the option --starter.disable-ipv6 is passed to the starter to use IPv4, then it will hang during startup.
Affected Versions: 0.14.3 (macOS only)
Fixed in Versions: -
Reference: N/A
Date Added: 2019-05-24
Component: Web UI
Deployment Mode: Active Failover
Description: The web interface shows a wrong replication mode in the replication tab in Active Failover deployments sometimes. It may display Master/Slave mode (the default value) because of timeouts if /_api/cluster/endpoints is requested too frequently.
Affected Versions: 3.5.x, 3.6.x
Fixed in Versions: -
Reference: N/A
Date Added: 2019-12-10
Component: Installer
Deployment Mode: All
Description: The DMG package for macOS is not notarized, which prevents the execution of ArangoDB3-CLI.app under macOS 10.15 (Catalina) with error message: “ArangoDB3-CLI can’t be opened because Apple cannot check it for malicious software”
Affected Versions: 3.3.x, 3.4.x, 3.5.x, 3.6.x
Fixed in Versions: -
Reference: arangodb/arangodb#10561
Date Added: 2020-01-07
Component: Installer
Deployment Mode: All
Description: V8-based binaries of the client packages (arangosh, arangoinspect, foxx-manager) have an incorrect default value for javascript.startup-directory and will thus not find the required JavaScript folder unless specified by the user.
Affected Versions: 3.4.x, 3.5.x, 3.6.0
Fixed in Versions: 3.4.9, 3.5.4, 3.6.1
Reference: arangodb/release-qa#183 (internal)
Date Added: 2020-01-07
Component: Installer
Deployment Mode: All
Description: The client packages for Windows miss the arangoinspect binary. As a workaround, you can run arangosh with the following options:
arangosh --server.authentication false --server.ask-jwt-secret --javascript.client-module inspector.js …
Affected Versions: 3.3.x, 3.4.x, 3.5.x, 3.6.0
Fixed in Versions: 3.3.25, 3.4.10, 3.5.5, 3.6.1
Reference: arangodb/arangodb#10835
Date Added: 2020-01-07
Component: Foxx
Deployment Mode: Cluster
Description: In case of a Foxxmaster failover, jobs in state 'progress' are not reset to 'pending' to restart execution.
Affected Versions: 3.4.x, 3.5.x, 3.6.x
Fixed in Versions: 3.4.10, 3.5.5, 3.6.1
Reference: arangodb/arangodb#10800