* add whitespace to make error message more readable
* Don't retry persisting follower information
for collections/shards already dropped.
The previous implementation retried (unsuccessfully in this case)
for up to 2 hours, occupying one scheduler thread.
* back port of agency call back cleanup
* storecallback missing
* revert callback bodies to API specification
* array needs be inside so that multiple unobserves to same key are possible
* clean up basic rocksdb statistics. More clean-up needed.
* add rocksdb throttle value to statistics
* update comments about rocksdb properties
* rename function per PR comments
* op:set should have new, some operators should not create non existing keys
* this is the proper direction
* observe/unobserve have no business in Node
* normalization of URI
* agency test added for observe / unobserve
* more tests
* Fixed catch tests.
* Added full index iterator utilization in case of some documents was not found in collection
* Added index operations reversal in case of insertion failure in rocksdb
* Removed singleop optimization as rollback possible even for such operations (in case of index operation failure on insert)
* Added tests for insert rollback in views
* Added catch tests for view block
* Added changelog entry
* fixed jslint errors
* fixed linux build
* Added test for update
* Fix CHANGELOG sequence
* Add line
* Added reverts for update and remove failures
* Cleanup in test. Added throwing error in case of failed reversal
* fixed typo
Co-Authored-By: Simran <Simran-B@users.noreply.github.com>
* fixed build
* Applied review comments
* Applied review comments
* Documentation 3.5/example generation improvements (#9498)
* Documentation/switch example generation to rocksdb (#9478)
* improve the formatting of the batch request documentation
* split to linewise, check whether we have a json and format it.
* Add missing asterisk
* Minor fixes / improvements
* jslint is your friend. (#9509)
* Update examples
* Fresh Swagger
* Bug fix/fix swagger datatype (#9045)
* remove http so https arangos will work
* verify that query parameters are proper swagger data types, fix offending documentation files
* return the actual type - not the list of available ones
* check formats
* there is no uint64 in swagger
* Fresh Swagger
* 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 error
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).