Known Issues in ArangoDB 3.7

This page lists important issues affecting the 3.7.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, 3.7.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, 3.7.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, 3.7.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, 3.7.x
Fixed in Versions: -
Reference: N/A
Date Added: 2020-03-19
Component: ArangoSearch
Deployment Mode: All
Description: Operators and functions in SEARCH clauses of AQL queries which compare values such as >, >=, <, <=, IN_RANGE() and STARTS_WITH() neither take the server language (--default-language) nor the Analyzer locale into account. The alphabetical order of characters as defined by a language is thus not honored and can lead to unexpected results in range queries.
Affected Versions: 3.5.x, 3.6.x
Fixed in Versions: -
Reference: arangodb/backlog#679 (internal)
Date Added: 2020-05-22
Component: ArangoSearch
Deployment Mode: Cluster
Description: The immediate recreation of ArangoSearch Analyzers in cluster deployments (deleting and shortly after creating one with the same name but different properties) causes errors in queries which involve such recreated Analyzers.
Affected Versions: 3.5.x, 3.6.x, 3.7.0, 3.7.0-1
Fixed in Versions: 3.7.1-alpha.1
Reference: arangodb/backlog#669 (internal), arangodb/backlog#695 (internal)
Date Added: 2020-06-16
Component: ArangoSearch
Deployment Mode: All
Description: The creation of Views in databases other than _system fails if the current user has no access to the default database. This is caused by the system which attempts to read from the global _analyzers collection without checking permissions first.
Affected Versions: 3.7.0
Fixed in Versions: 3.7.1
Reference: arangodb/backlog#669 (internal), arangodb/arangodb#11849
Date Added: 2020-07-31
Component: ArangoSearch
Deployment Mode: All
Description: AQL queries with subqueries or joins in SEARCH expressions may return incorrect results. As a workaround, you can disable the optimizer rule which causes the problem with the following query options: { optimizer: { rules: [ "-inline-subqueries" ] } }
Affected Versions: 3.5.x, 3.6.x, 3.7.x
Fixed in Versions: -
Reference: arangodb/arangodb#12247
Date Added: 2020-07-31
Component: ArangoSearch
Deployment Mode: All
Description: The STARTS_WITH() and PHRASE() ArangoSearch functions don’t accept an array of prefixes / phrase parts as intended.
Affected Versions: 3.7.x
Fixed in Versions: -
Reference: arangodb/backlog#741 (internal), arangodb/backlog#738 (internal)
Date Added: 2020-07-31
Component: ArangoSearch
Deployment Mode: All
Description: The LEVENSHTEIN_MATCH() ArangoSearch function incorrectly calculates the Damerau-Levenshtein distance if the distance is greater than 4 and pure Levenshtein distance is requested.
Affected Versions: 3.7.x
Fixed in Versions: 3.7.2
Reference: arangodb/backlog#731 (internal)
Date Added: 2020-07-31
Component: ArangoSearch
Deployment Mode: All
Description: Wildcard searches like "%a%b_c%" may not match all indexed terms (e.g. "aQWEQbbQcDDDFS").
Affected Versions: 3.7.x
Fixed in Versions: 3.7.2
Reference: arangodb/backlog#732 (internal)

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, 3.7.x
Fixed in Versions: -
Reference: arangodb/arangodb#6399
Date Added: 2020-07-22
Component: AQL
Deployment Mode: Cluster
Description: When explicitly destroying an AQL Cursor created with stream: true in a cluster deployment, the server does not reply (the request hangs forever).
Affected Versions: 3.6.x, 3.7.0
Fixed in Versions: 3.7.1
Reference: BTS-126 (internal)

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, 3.7.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, 3.7.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, 3.7.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, 3.7.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, 3.7.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, 3.7.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, 3.7.x
Fixed in Versions: -
Reference: N/A
Date Added: 2019-03-17
Component: Schema Validation
Deployment Mode: All
Description: The schema validation cannot pin-point which part of a rule made it fail. This is under investigation but very hard to solve for complex schemas. For example, when using not and anyOf, this would result in trees of possible errors. For now users should fall back to tools like jsonschemavalidator.net
Affected Versions: 3.7.x
Fixed in Versions: -
Reference: N/A
Date Added: 2019-03-17
Component: Schema Validation
Deployment Mode: All
Description: Remote schemas are not supported for security reasons. This limitation will likely remain unfixed.
Affected Versions: 3.7.x
Fixed in Versions: -
Reference: N/A
Date Added: 2019-04-03
Component: arangod
Deployment Mode: Cluster
Description: Updating the properties of a collection in the cluster may return before the properties are updated consistently on all shards. This is especially visible when setting a schema for a collection with multiple shards, and then instantly starting to store non-conforming documents into the collection. These may be accepted until the properties change has been fully propagated to all shards.
Affected Versions: 3.7.x
Fixed in Versions: -
Reference: N/A
Date Added: 2020-04-23
Component: arangod
Deployment Mode: Cluster
Description: The creation of example graphs fails if --cluster.min-replication-factor is set to a value greater than 1, because the system attempts to create the collections with a replication factor of 1 despite the higher minimum.
Affected Versions: 3.6.x, 3.7.0, 3.7.0-1
Fixed in Versions: 3.6.4, 3.7.1-alpha.1
Reference: arangodb/arangodb#11487
Date Added: 2020-06-19
Component: SmartGraphs
Deployment Mode: Cluster
Description: When inserting edges into an edge collection of a SmartGraph, the auto-generated _rev values for the ingoing and outgoing part of the edge may differ. This can be confusing when querying the _rev values of the edges later.
Affected Versions: 3.4.x, 3.5.x, 3.6.x, 3.7.x
Fixed in Versions: 3.6.5, 3.7.1
Reference: N/A
Date Added: 2019-06-25
Component: Schema Validation
Deployment Mode: All
Description: When using arangorestore for a collection with a defined schema, schema validation is not executed.
Affected Versions: 3.7.x
Fixed in Versions: -
Reference: N/A
Date Added: 2020-06-30
Component: SmartGraphs
Deployment Mode: Cluster
Description: Changing the collection properties of a smart edge collection did not propagate the changes to child collections for the waitForSync, cacheEnabled and schema attributes. This has been fixed in 3.7.1 for new smart edge collections, created with 3.7.1 or later.
Affected Versions: 3.4.x, 3.5.x, 3.6.x, 3.7.x
Fixed in Versions: 3.7.1
Reference: arangodb/arangodb#12065
Date Added: 2020-07-31
Component: Web UI
Deployment Mode: All
Description: The API tab of Foxx services does not render the Swagger UI interface.
Affected Versions: 3.6.x, 3.7.x
Fixed in Versions: 3.6.6, 3.7.1
Reference: arangodb/arangodb#12297
Date Added: 2020-07-31
Component: Web UI
Deployment Mode: All
Description: The web interface confirms the creation of an index, but then displays an error 404: Not Found despite of a successful index creation.
Affected Versions: 3.6.x, 3.7.x
Fixed in Versions: 3.6.6, 3.7.1
Reference: arangodb/arangodb#12248
Date Added: 2020-07-31
Component: arangosync
Deployment Mode: DC2DC
Description: No JWT rotation takes place with the included arangosync (v0.7.8). If ArangoDB rotates the JWT secret, arangosync processes must be restarted (with the new JWT secret for ArangoDB) if datacenter to datacenter replication is required. That may trigger full resync.
Affected Versions: 3.7.x
Fixed in Versions: 3.6.6, 3.7.2
Reference: N/A
Date Added: 2020-07-31
Component: ArangoDB Starter
Deployment Mode: All
Description: The included ArangoDB Starter version does not support JWT secret rotation. In addition, there is no way to set the arangod option server.jwt-secret-keyfile (via option pass-through capability of the Starter) because the Starter either ignores it (if no --auth.jwt-secret was used) or blocks it with an error (Pass through option --server.jwt-secret-keyfile conflicts with automatically generated option with value).
Affected Versions: 3.7.x
Fixed in Versions: -
Reference: BTS-124 (internal)
Date Added: 2020-07-31
Component: arangosync
Deployment Mode: DC2DC
Description: A OneShard cluster deployment can currently not be combined with datacenter to datacenter replication.
Affected Versions: 3.6.x, 3.7.x
Fixed in Versions: -
Reference: N/A