* use the default arangosh client connection instead of the simple http client to test the gharial API
* refrain using globals, as sugested by @goedderz
* add method to check whether there already is a reply present
* fix result handling, return errors & set results
* the mock also needs to implement the 'isEmpty' function
* Update arangod/RestHandler/RestGraphHandler.cpp
Co-Authored-By: Michael Hackstein <michael@arangodb.com>
* Update arangod/RestHandler/RestGraphHandler.cpp
Co-Authored-By: Michael Hackstein <michael@arangodb.com>
* Update lib/Rest/VstResponse.h
Co-Authored-By: Michael Hackstein <michael@arangodb.com>
* Update lib/Rest/HttpResponse.h
Co-Authored-By: Michael Hackstein <michael@arangodb.com>
* changelog
* backport: fix variable name
* adjust test to corrected API
* make it private
* fix indention
* Update CHANGELOG
* Bugfix for recurring Jenkins error in api-simple-modify-example-cluster-spec.rb (#10190)
DependencyProxy::skipSome did not work correctly with multiple
dependencies if atMost was reached, returning DONE early.
* Updated CHANGELOG
* Deleted CHANGELOG entry
* Added regression test for #10190
* Added missing include
* Fixed repeatable seek to the same document
* Fix. Multiple conjuncts in conjunction.
* Added CHANGELOG for the issue #10090.
* A new line in CHANGELOG.
* Add tests
* honor sharding restrictions also when creating a graph with existing
collections
* add test
* additional validation for startup parameters
* fixed logIDs
* 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.
* 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.
* 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
* Bug fix/issue #9612 (#9764)
* Fixed ViewExecutionNode retrieval with deleted documents present in view
* Ported solution from 3.4 branch
* Changed index store in collection from vector to set. To make reversable indexes always last to execute
* Fixed re-enter hung
* Index storage fix
* Made index order deterministic
* Fix Mac build
* Added tests for index reversal
* Fixed Mac build
* Code cleanup
* Some cleanup
* Removed some redundand copy constructor calls
* Applied review comments
* Applied review comments
* Update CHANGELOG
* Update CHANGELOG
* make index selection more deterministic
* updated CHANGELOG
* serialize indexes used by traversal with their estimates
* serialize selectivity estimates for shortest path nodes too
* fix assertion that doesn't hold true in unit tests
* fix test
Wilfried Goesgens
Jan
Tobias Gödderz
Iurii Popov
Max Neunhöffer
Heiko
KVS85
Frank Celler
Dronplane
Michael Hackstein
Dan Larkin-York
Jan Christoph Uhde
Simon
Lars Maier