Deprecated

    • MMFiles Storage Engine: The MMFiles storage engine was deprecated in version 3.6.0 and removed in 3.7.0. To change your MMFiles storage engine deployment to RocksDB, see: Switch storage engine

      MMFiles specific startup options still exist but will also be removed. This will affect the following options:

      • --database.force-sync-properties
      • --database.index-threads
      • --database.maximal-journal-size
      • --database.throw-collection-not-loaded-error
      • --wal.*

      The collection attributes doCompact, indexBuckets, isVolatile, journalSize and path are only used with MMFiles and are thus also deprecated.

    • Simple Queries: Idiomatic interface in arangosh to perform trivial queries. They are superseded by , which can also be run in arangosh. AQL is a language on its own and way more powerful than Simple Queries could ever be. In fact, the (still supported) Simple Queries are translated internally to AQL, then the AQL query is optimized and run against the database in recent versions, because of better performance and reduced maintenance complexity.

    • Actions: Snippets of JavaScript code on the server-side for minimal custom endpoints. Since the Foxx revamp in 3.0, it became really easy to write Foxx Microservices, which allow you to define custom endpoints even with complex business logic.

      You can still find the in 3.4 or older versions of the documentation.

    • Outdated AQL functions: The following AQL functions are deprecated and their usage is discouraged:

      • IS_IN_POLYGON
      • NEAR
      • WITHIN

      See Geo functions for substitutes.

    • Overwrite option: The overwrite option for insert operations (either single document operations or AQL INSERT operations) is deprecated in favor of the option, which provides more flexibility.

    • minReplicationFactor collection option: The minReplicationFactor option for collections has been renamed to writeConcern. If minReplicationFactor is specified and no writeConcern is set, the minReplicationFactor value will still be picked up and used as writeConcern value. However, this compatibility mode will be removed eventually, so changing applications from using minReplicationFactor to writeConcern is advised.

    • The following arangod startup options are deprecated and will be removed in a future version:

      • --server.jwt-secret (use --server.jwt-secret-keyfile)

      The following options are deprecated for arangorestore:

      • --default-number-of-shards (use --number-of-shards instead)
      • --default-replication-factor (use --replication-factor instead)

      The following startup options are deprecated in arangod and all client tools:

      • --log (use --log.level instead)
      • --log.use-local-time (use --log.time-format instead)
      • (use --log.time-format instead)
      • --log.performance (use --log.level instead)

    • Obsoleted startup options: Any startup options marked as obsolete can be removed in any future version of ArangoDB, so their usage is highly discouraged. Their functionality is already removed, but they still exist to prevent unknown startup option errors.

    • JavaScript traversal API: The is deprecated since version 3.4.0. The JavaScript traversal module @arangodb/graph/traversal is also deprecated since then. The preferred way to traverse graphs is via AQL.

      • arangodb::GRAPH_VERTICES
      • arangodb::GRAPH_NEIGHBORS
      • arangodb::GRAPH_COMMON_NEIGHBORS
      • arangodb::GRAPH_COMMON_PROPERTIES
      • arangodb::GRAPH_PATHS
      • arangodb::GRAPH_SHORTEST_PATH
      • arangodb::GRAPH_DISTANCE_TO
      • arangodb::GRAPH_ABSOLUTE_ECCENTRICITY
      • arangodb::GRAPH_ECCENTRICITY
      • arangodb::GRAPH_ABSOLUTE_CLOSENESS
      • arangodb::GRAPH_CLOSENESS
      • arangodb::GRAPH_ABSOLUTE_BETWEENNESS
      • arangodb::GRAPH_BETWEENNESS