Commit Graph

4 Commits

Author SHA1 Message Date
Eddie Louie
9fc1ecd711 SERVER-26315 Override DBCollection.prototype.drop to re-shard collections that are dropped
This reverts commit fb956b3b0a.
2017-03-23 14:07:50 -04:00
Randolph Tan
fb956b3b0a Revert "SERVER-26315 Override DBCollection.prototype.drop to re-shard collections that are dropped"
This reverts commit 56e66454d1.

Conflicts:
	buildscripts/resmokeconfig/suites/sharded_collections_jscore_passthrough.yml
2017-03-23 13:56:21 -04:00
Eddie Louie
56e66454d1 SERVER-26315 Override DBCollection.prototype.drop to re-shard collections that are dropped
in sharded cluster environments.
2017-03-15 19:19:49 -04:00
David Storch
82b16740f8 SERVER-19758 add support for "executionStats" and "allPlansExecution" to agg explain
Like other explainable commands, aggregate can now be
explained using the explain command, e.g.
db.runCommand({explain: {aggregate: ...}, verbosity:
"executionStats"}). The existing explain:true flag
corresponds to "queryPlanner" mode and is still supported.
However, explain:true cannot be specified when explaining
aggregate via the explain command.

Additional execution information is provided only in the
$cursor section of the aggregation explain output. Having
aggregation stages themselves track and report execution
info is further work.
2017-03-13 09:46:14 -04:00