* remove some non-unused V8 persistents
* do not throw that many bogus assertions
* do not rely on server role being defined
* slightly better debug output for V8 context debugging
* fix collection ids in inventory response
* simplify bootstrap a bit
* slightly better error handling
* make elapsed time a queryable value
* use less memory for stub collections
* added assertions that will always make sense
* added assertions
* do not garbage-collect while waiting
* less copying of parameters
* do not show "load indexes into memory" buttons for mmfiles engine
as all indexes are in memory anyway
* when a collection is truncated via the web interface, flush the WAL and rotate all active journals
this will make close all open journals on leader and followers and make them subject to compaction opportunities
* fix invalid server id values being passed from web interface to backend
* introduce afterTruncate method for indexes
* added test case for issue #3447
* updated CHANGELOG
* don't warn about replicationFactor for system collections
* check that the queries actually use the geo index and not some other index
* properly report error in web interface
* fix some internals checks that made truncate fail for bigger collections in maintainer mode
* also run a compact() operation after a serious truncate
in order to make iteration over the truncated range much faster
when the collection is next accessed
* increase default maximum number of V8 contexts to at least 16
* Make isRestore work in the cluster.
This covers sharded collections with default sharding and non-default
sharding.
* always use locally generate revision ids for storing and looking up documents
* remove API docs for endpoints that were deleted in 3.0
* remove unused variable
* set all scalar values in the ctor, so check tools do not complain
* move Result objects
* prevent potential nullptr access
* remove ambiguous boolean parameter with no clear meaning
* make code check tools happy
* don't allow copying cache Findings, allow moving Results
* the debug functionality for counting RocksDB key ranges was broken
this produced sporadic test failures
* remove superfluous iostream include
* fix range checks
* don't leak if an error happens during database removal
* try to simplify Result a bit
* try to deletion checks a bit more robust
* simplify index API a bit
* fix fulltext index removal performance, simplified code
* updated CHANGELOG
* fix hanging test
* try to fix shutdown problem
* improve fulltext query performance
* fixed duplicate var
* removed obsolete code
* fix some shutdown races
* do not call ensureIndex that often
* cleaning up several duplicate versions of Index::memory, Index::cleanup, Index::drop, integrating branch issue-383-ensure-delete
* fixing wrong column family
* Testing hash for documents
* fixing logspam error
* added base support for kHash in the edge index
* Current version of hash enabled edge index
* removed rocksdb key type byte, dynamic prefixes for hash-index
* Fixing issues with key classes
* Fixing merge conflict
* Fixing version with semi-working hash index
* fixing various issues
* Fixing hanger in EdgeIndexIterator nextExta, when _cache is disabled. Reenable cache
* Fixing geo index bounds, and fillIndexes error handling
* Adding back failure point
* Fixing RocksDBKey::vertexId
* Added version check on startup
* Fixing version check
* added one more check
* properly detect column families at startup
* Adding additional sanity checking
* Adding missing column family
* some fixes
* Turned off geoindex sync
* fixed error
* added asserts (untested)
* Adding more asserts
* Augmented cache API and fixed a potential deadlock scenario.
* The RocksDBEdgeIndex now tries to read up to 10 times form the cache on lock_timeout. Instead of rewriting everything after first attempt
KVS85
Wilfried Goesgens
Frank Celler
Simon
Jan Christoph Uhde
Jan
Vasiliy
Dan Larkin
Michael Hackstein
jsteemann
Jan Christoph Uhde