* fixed ui behaviour when replacing a foxx app
* Bug fix/curb aardvark foxx cthulhu (#9867)
* Revert "fixed ui behaviour when replacing a foxx app"
This reverts commit 6092465e05d11c10e83e3424945d8bf9e8f3ddaa.
* Cleanup on aisle 3
* Typo
* Fixed param order
* Cleanup flags
* Actually use the queryParams
* currently not supported via grunt env
* changelog
* removed not needed view
* fixed wrong used function
* Added regression test for consecutive constrained sorts
* Bugfix: sort-limit rule skipped too many node types
* Added CHANGELOG entry
* Apply sort-limit rule before single document operations
* validate collection when leasing an existing transaction
* use WITH statement
* allow implicit read collections again
* simplify collection name validation
* re-implement it
* remove dead code
* remove unused method
* apply review comments
* whoops, deleted too many methods
* fixit
* Squashed commit of feature-3.5/hotbackup_devel.
This puts hotbackup into 3.5.
* Port atomic-database-creation-2 to 3.5.
* Remove some wrongly ported code.
* Fix compilation.
* Fix a manual merge error.
* Remove a feature from the mocks which does not exist in 3.5.
* Add some code which was forgotten in manual merge.
* Fix a problem introduced in a manual merge.
* reuse function
* Address some whitespace issues that came up in review
* aardvark should not create the frontend collection
* create _frontend collection from c++
* recheckAndUpdate Callback in CollectionWatcher
* Wrong author ;)
* rm outdated todo
* Update lib/Basics/VelocyPackHelper.h
Co-Authored-By: Michael Hackstein <michael@arangodb.com>
* use logger unique id, use startup logger
* not needed
* optimized vector shardid method
* do not create _modules collection lazy anymre
* Formatting.
* Assert instead of if/TRI_ASSERT(false)
* Don't use exceptions as control structure
* Re-add READ_LOCKER that got lost in translation
* Fix audit log in case database creation fails early.
* legacy sharding
* Add CHANGELOG entry.
* Retry database cancellation indefinitely
* Do not use exceptions in UpgradeTask
* DropCollection is a FAST_LANE action and should not need much time or else retry.
* Remove superflous addition of LdapFeature
Proudly brought to you by ASAN tests
* Fixed check for distributShardsLike sharding on _system database
* Fixed compile issue on tests
* Removed assertion that seems to be not correct yet on devel.
* Sort out google cloud storage as remote. (#9918)
* Add successful method to ClusterCommResult.
* Improve error forwarding for cluster internal communication.
* Feature/hotbackup list retries (#9924)
* retry hot backup listing for 2 minutes in cluster before giving up
* Enable api by default.
* always create statistics collections & indices & fishbowl
* fix broken list of non existing id (#9957)
* Fix compilation after manual merge.
* Fix another compilation problem.
* Yet more fixes for compilation.
* More compilation fixes.
* Removed forgotten, illegal if.
* Removed obsolete include
* Squashed commit of feature-3.5/hotbackup_devel.
This puts hotbackup into 3.5.
* Port atomic-database-creation-2 to 3.5.
* Remove some wrongly ported code.
* Fix compilation.
* Fix a manual merge error.
* Remove a feature from the mocks which does not exist in 3.5.
* Add some code which was forgotten in manual merge.
* Fix a problem introduced in a manual merge.
* reuse function
* Address some whitespace issues that came up in review
* aardvark should not create the frontend collection
* create _frontend collection from c++
* recheckAndUpdate Callback in CollectionWatcher
* Wrong author ;)
* rm outdated todo
* Update lib/Basics/VelocyPackHelper.h
Co-Authored-By: Michael Hackstein <michael@arangodb.com>
* use logger unique id, use startup logger
* not needed
* optimized vector shardid method
* do not create _modules collection lazy anymre
* Formatting.
* Assert instead of if/TRI_ASSERT(false)
* Don't use exceptions as control structure
* Re-add READ_LOCKER that got lost in translation
* Fix audit log in case database creation fails early.
* legacy sharding
* Add CHANGELOG entry.
* Retry database cancellation indefinitely
* Do not use exceptions in UpgradeTask
* DropCollection is a FAST_LANE action and should not need much time or else retry.
* Remove superflous addition of LdapFeature
Proudly brought to you by ASAN tests
* Fixed check for distributShardsLike sharding on _system database
* Fixed compile issue on tests
* Removed assertion that seems to be not correct yet on devel.
* Sort out google cloud storage as remote. (#9918)
* Add successful method to ClusterCommResult.
* Improve error forwarding for cluster internal communication.
* Feature/hotbackup list retries (#9924)
* retry hot backup listing for 2 minutes in cluster before giving up
* Enable api by default.
* fix broken list of non existing id (#9957)
* Fix compilation after manual merge.
* Fix another compilation problem.
* Yet more fixes for compilation.
* More compilation fixes.
* added proper UI support for collections using smartGraphAttribute or smartGraphAttribute
* make key selection more clear
* added awesome ' : ' div
* fixed smart doc creation logic
* changelog
* don't make index selectivity estimate requests fail inside cluster
transactions
* improve logging, and don't make transactions more robust
don't make transaction operations fail immediately if they cannot
acquire the transaction lock instantly. it is somewhat expected that
sometimes the garbage collection comes in-between and acquires locks
for a short amount of time - this should not lead to failures in
other operations on the transaction
* fix a race for transaction leases
* fix test failure
* moved functionality into shutdownExecute
* avoid lookup plus sequent insert/emplace for the fast path
additionally add transaction id and more location information to
error messages which were previously undistinguishable
* Revert "avoid lookup plus sequent insert/emplace for the fast path"
This reverts commit 11b27c338940a9fc203dbdb35713845c407a902d.
* revert most stuff, only leave improved logging there
* restore _users collection at the very end only,
because updating documents in _users may change the credentials
for the arangorestore user itself, which may lead to all follow-up
requests by arangorestore being rejected with "authorized"/"forbidden"
* updated CHANGELOG
* DropCollection is a FAST_LANE action and should not need much time or else retry.
* DropCollection is a FAST_LANE action and should not need much time or else retry.
* Update CHANGELOG