From 82b16740f8a66093b453a73a04b3b9bd00e5d7a0 Mon Sep 17 00:00:00 2001 From: David Storch Date: Fri, 10 Feb 2017 11:52:18 -0500 Subject: 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. --- src/mongo/db/pipeline/document_source_sort_by_count_test.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/mongo/db/pipeline/document_source_sort_by_count_test.cpp') diff --git a/src/mongo/db/pipeline/document_source_sort_by_count_test.cpp b/src/mongo/db/pipeline/document_source_sort_by_count_test.cpp index 82e4aa6fb56..3e0a007c59b 100644 --- a/src/mongo/db/pipeline/document_source_sort_by_count_test.cpp +++ b/src/mongo/db/pipeline/document_source_sort_by_count_test.cpp @@ -68,7 +68,7 @@ public: // Serialize the DocumentSourceGroup and DocumentSourceSort from $sortByCount so that we can // check the explain output to make sure $group and $sort have the correct fields. - const bool explain = true; + const auto explain = ExplainOptions::Verbosity::kQueryPlanner; vector explainedStages; groupStage->serializeToArray(explainedStages, explain); sortStage->serializeToArray(explainedStages, explain); -- cgit v1.2.1