Known Issues in ArangoDB 3.5

This page lists important issues affecting the 3.5.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

Purge Analyzer cache

To fix query errors caused by an immediately re-created Analyzer, the DB-Servers need to be forced to clear their Analyzer caches. This can be achieved by using below code in arangosh:

1. Connect to a Coordinator with arangosh
2. var analyzers = require("@arangodb/analyzers");
3. analyzers.remove("<PROBLEMATIC ANALYZER>");
4. var dummy = "dummy_analyzer_" + Date.now();
5. analyzers.save(dummy, "identity", {});

6. db._query("FOR d IN <ANY EXISTING VIEW> SEARCH ANALYZER(STARTS_WITH(d.test, 'something'), @a) RETURN d", {a: dummy});

   This query with a new Analyzer will force cache purging. If this query reports an error about a missing Analyzer, then wait for a minute and retry until it succeeds.

7. Re-create your Analyzer (<PROBLEMATIC ANALYZER>) with the new, correct properties.
8. analyzers.remove(dummy);
9. Check if the original query still fails. It is possible that it reports a missing Analyzer, but the problem should go away in a minute and the query execute normally.

AQL

Upgrading

Stream Transactions

Hot Backup

Other