Arangodb client application
Server startup: the recommended value for the Linux kernel setting in /proc/sys/vm/max_map_count was increased to a value eight times as high as in 3.2. Using it will make arangod log a warning on startup. The startup configuration parameter -cluster.my-local-info is deprecated now.
![arangodb client application arangodb client application](https://www.arangodb.com/wp-content/uploads/2020/03/Opentext_logo.png)
For compatibility reasons, ArangoDB 3.3 will not fail on startup if the option is still used in the configuration, but it will silently ignore this option.
![arangodb client application arangodb client application](https://www.arangodb.com/wp-content/uploads/2015/04/export_api-300x159.png)
The startup configuration parameter -cluster.my-id does not have any effect in 3.3. As linking to non-existing vertices may indicate an issue in/with the data model or the client application, the warning is registered in the query so client applications have access to it.ĪrangoDB usernames must not start with the string :role. If a non-existing vertex is referenced from a traversal, it is not desirable to log errors as ArangoDB can store edges pointing to non-existing vertices (which is perfectly valid if the low-level insert APIs are used).
![arangodb client application arangodb client application](https://raw.githubusercontent.com/docker-library/docs/fc374e65196006a9b55da56446332f953f3c88b3/arangodb/logo.png)
The following incompatible changes have been made in ArangoDB 3.3:ĪQL: during a traversal if a vertex is not found, arangod will not log an error and continue with a NULL value, but will instead register a warning at the query and continue with a NULL value. It is recommended to check the following list of incompatible changes before upgrading to ArangoDB 3.3, and adjust any client programs if necessary.