* restrict-to-single-shard - improves changelog
* Update CHANGELOG
Still missing an explanation what dumping & restoring actually does - I assume because documents can be incorrectly sharded and we don't support re-sharding?
* Added tests for dump-restore of SmartGraphs
* Arangosh will now expose isSmart and the smartGraphAttribute on properties
* RestReplicationHandler will now ignore smart-graph collections unless you execute it with force
* Added changelog
* Reactivated original mmfiles dump/restore test
* Skip hidden smart graph collections in arangodump
* Do not dump shadowCollections metadata of smart edge collections
* Cluster optimizer rules for soerted gather nodes now handle virtual edge collections correctly
* Added a dump/restore tests for smartgraphs in rocksdb as well
* Deactivated checks for writesExecuted statistics in dump/restore tests for smartgraphs mmfiles
* Really exclude shadowCollections
* Reduced loglevel
* Added tests
* Don't change single-server behaviour
* Fix tests for omitted shadowCollections and hidden collections
* Activated statistics in MMFIles dump test again and included isEnterprise in rocksdb dump test
* A modification node can now disableStatistics, which means it does not contribute to query->extras() this is only relevant in SmartGraph case so far.
* Added a test to dump&restore satellite collections
* Bugfix: restore satellite collections properly
* Added regression test for internal issue #2237
* Fix bug #2237
* Updated CHANGELOG
* Copied dump/restore tests to rockdsb
* Removed enterprise test
* Added inline comment for smart-edge collections in optimizer rules
* Removed duplicate CHANGELOG entry
* Simplified removal of shadowCollections
query = "FOR doc IN @@collection FILTER doc.value > @value RETURN doc";
bind = { value: 42, "@collection": "mycollection" };
options = { examples: 10, anonymize: true };
require("@arangodb/aql/explainer").debugDump("/tmp/query-debug-info", query, bind, options);
Entitled users can send the generated file to the ArangoDB support to facilitate
reproduction and debugging.
The data from the generated file can be restored and analyzed via the *inspectDump*
function:
require("@arangodb/aql/explainer").inspectDump("/tmp/query-debug-info");
* multiple cluster-related AQL optimizations
* do not apply single-shard optimization if _includedShards is already set from the outside
* implement changes requested by @mchacki
* bump version number for all local DDL changes and tell agency
this allows other listeners (e.g. for DC2DC) to get notified when
DDL operations are carried out locally and need to be applied remotely
* Increase a log level.
* Added a test asserting the last followers are removed first as required by moveShard
* Remove the last followers first
* Removed unused includes
* Updated CHANGELOG
* fixed internal issue 2102: Segfaults in arangod console when using agency functions in single server mode
* make more ops fail when invoking them in non-cluster mode