« Changelog History


ArangoDB v3.3.3 Release Notes

Release Date: 2018-01-16 // over 6 years ago

    • 🛠 fix issue #4272: VERSION file keeps disappearing

    • 🛠 fix internal issue #81: quotation marks disappeared when switching table/json editor in the query editor ui

    • ➕ added option --rocksdb.throttle to control whether write-throttling is enabled Write-throttling is turned on by default, to reduce chances of compactions getting too far behind and blocking incoming writes.

    • 🛠 fixed issue #4308: Crash when getter for error.name throws an error (on Windows)

    • 📜 UI: fixed a query editor caching and parsing issue

    • 🛠 Fixed internal issue #1683: fixes an UI issue where a collection name gets wrongly cached within the documents overview of a collection.

    • 🛠 Fixed an issue with the index estimates in RocksDB in the case a transaction is aborted. Former the index estimates were modified if the transaction commited or not. Now they will only be modified if the transaction commited successfully.

    • ⚡️ UI: optimized login view for very small screen sizes

    • Truncate in RocksDB will now do intermediate commits every 10.000 documents if truncate fails or the server crashes during this operation all deletes that have been commited so far are persisted.

    • 0️⃣ make the default value of --rocksdb.block-cache-shard-bits use the RocksDB default value. This will mostly mean the default number block cache shard bits is lower than before, allowing each shard to store more data and cause less evictions from block cache

    • issue #4222: Permission error preventing AQL query import / export on webui

    • ⚡️ UI: optimized error messages for invalid query bind parameter

    • ⬆️ UI: upgraded swagger ui to version 3.9.0

    • ⏪ issue #3504: added option --force-same-database for arangorestore

    with this option set to true, it is possible to make any arangorestore attempt fail if the specified target database does not match the database name specified in the source dump's "dump.json" file. it can thus be used to prevent restoring data into the "wrong" database

    The option is set to false by default to ensure backwards-compatibility

    • 0️⃣ make the default value of --rocksdb.block-cache-shard-bits use the RocksDB default value. This will mostly mean the default number block cache shard bits is lower than before, allowing each shard to store more data and cause less evictions from block cache

    • 🛠 fixed issue #4255: AQL SORT consuming too much memory

    • 🛠 fixed incorrect persistence of RAFT vote and term