diff options
| author | David Storch <david.storch@10gen.com> | 2017-02-10 11:52:18 -0500 |
|---|---|---|
| committer | David Storch <david.storch@10gen.com> | 2017-03-13 09:46:14 -0400 |
| commit | 82b16740f8a66093b453a73a04b3b9bd00e5d7a0 (patch) | |
| tree | 62d156fc9676526ecbea19cd03ef7a293579c4df /src/mongo/db/commands.cpp | |
| parent | 73f9e8b8a8422becf8694fe3d82c0e647dc71189 (diff) | |
| download | mongo-82b16740f8a66093b453a73a04b3b9bd00e5d7a0.tar.gz | |
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.
Diffstat (limited to 'src/mongo/db/commands.cpp')
| -rw-r--r-- | src/mongo/db/commands.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mongo/db/commands.cpp b/src/mongo/db/commands.cpp index e726bb3918a..12e60527080 100644 --- a/src/mongo/db/commands.cpp +++ b/src/mongo/db/commands.cpp @@ -146,7 +146,7 @@ void Command::help(stringstream& help) const { Status Command::explain(OperationContext* opCtx, const string& dbname, const BSONObj& cmdObj, - ExplainCommon::Verbosity verbosity, + ExplainOptions::Verbosity verbosity, const rpc::ServerSelectionMetadata& serverSelectionMetadata, BSONObjBuilder* out) const { return {ErrorCodes::IllegalOperation, str::stream() << "Cannot explain cmd: " << getName()}; |