arangodb/Documentation/Books/Manual/ReleaseNotes/KnownIssues34.md

Known Issues in ArangoDB 3.4

This page lists important issues affecting the 3.4.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-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.0-RC.5 Fixed in Versions: - Reference: arangodb/backlog#508 (internal)
Date Added: 2018-12-03 Component: ArangoSearch Deployment Mode: Cluster Description: ArangoSearch index consolidation does not work during creation of a link on existing collection which may lead to massive file descriptors consumption Affected Versions: 3.4.0-RC.5 Fixed in Versions: - Reference: arangodb/backlog#509 (internal)
Date Added: 2018-12-03 Component: ArangoSearch Deployment Mode: Cluster Description: Long-running DML transactions on collections (linked with ArangoSearch view) block "ArangoDB flush thread" making impossible to refresh data "visible" by a view Affected Versions: 3.4.0-RC.5 Fixed in Versions: - Reference: arangodb/backlog#510 (internal)
Date Added: 2018-12-03 Component: ArangoSearch Deployment Mode: All Description: ArangoSearch index format included starting from 3.4.0-RC.4 is incompatible to earlier released 3.4.0 release candidates. Dump and restore is needed when upgrading from 3.4.0-RC.4 to a newer 3.4.0.x release Affected Versions: 3.4.0-RC.5 Fixed in Versions: - Reference: N/A
Date Added: 2018-12-03 Component: ArangoSearch Deployment Mode: All Description: RocksDB recovery fails sometimes after renaming a view Affected Versions: 3.4.0-RC.5 Fixed in Versions: - Reference: arangodb/backlog#469 (internal)
Date Added: 2018-12-03 Component: ArangoSearch Deployment Mode: All Description: ArangoSearch ignores _id attribute even if includeAllFields is set to true Affected Versions: 3.4.0-RC.5 Fixed in Versions: - Reference: arangodb/backlog#445 (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.0-RC.5 Fixed in Versions: - Reference: arangodb/backlog#318 (internal)
Date Added: 2018-12-03 Component: ArangoSearch Deployment Mode: All Description: Using score functions (BM25/TFIDF) in ArangoDB expression is not supported Affected Versions: 3.4.0-RC.5 Fixed in Versions: - Reference: arangodb/backlog#316 (internal)
Date Added: 2018-12-03 Component: ArangoSearch Deployment Mode: All Description: ArangoSearch index format included starting from 3.4.0-RC.3 is incompatible to earlier released 3.4.0 release candidates. Dump and restore is needed when upgrading from 3.4.0-RC.2 to a newer 3.4.0.x release Affected Versions: 3.4.0-RC.5 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.0-RC.5 Fixed in Versions: - Reference: arangodb/arangodb#6399

Other

Issue

Date Added: 2018-12-04 Component: arangod Deployment Mode: All Description: Parallel creation of collections using multiple client connections with the same database user may spuriously fail with "Could not update user due to conflict" warnings when setting user permissions on the new collections. A follow-up effect of this may be that access to the just-created collection is denied. Affected Versions: 3.4.0 Fixed in Versions: 3.4.1 Reference: arangodb/arangodb#5342