ArangoDB v3.5.0-rc.7 Release Notes

Release Date: 2019-08-01 // almost 5 years ago
    • โฌ†๏ธ Upgraded arangodb starter version to 0.14.12.

Previous changes from v3.5.0-rc.6

    • ๐Ÿ›  Fixed issue #9459: Optimization rule remove-collect-variables does not KEEP all necessary data.

    • โž• Added gzip and encryption options to arangoimport and arangoexport.

    • โž• Added missing REST API route GET /_api/transaction for retrieving the list of currently ongoing transactions.

    • ๐Ÿ›  Fixed issue #9558: RTRIM not working as expected.

    • โž• Added startup error for bad temporary directory setting.

    If the temporary directory (--temp.path) setting is identical to the database directory (--database.directory) this can eventually lead to data loss, as temporary files may be created inside the temporary directory, causing overwrites of existing database files/directories with the same names. Additionally the temporary directory may be cleaned at some point, and this would lead to an unintended cleanup of the database files/directories as well. Now, if the database directory and temporary directory are set to the same path, there will be a startup warning about potential data loss (though in ArangoDB 3.4 allowing to continue the startup - in 3.5 and higher we will abort the startup).

    • ๐Ÿ‘‰ Make TTL indexes behave like other indexes on creation.

    If a TTL index is already present on a collection, the previous behavior was to make subsequent calls to ensureIndex fail unconditionally with the error "there can only be one ttl index per collection".

    Now we are comparing the attributes of the to-be-created index with the attributes of the existing TTL index and make it only fail when the attributes differ. If the attributes are identical, the ensureIndex call succeeds and returns the existing index.