MongoDB聚合explain仅返回前阶段信息，如何查看全管道步骤详情？

Hey there! Let's break down what's happening here and how to get the full aggregation pipeline details you're looking for.

First, why you're seeing only partial stages and getting that cursor error #

1. Automatic $match merging: MongoDB's query optimizer automatically combines consecutive $match stages into a single stage to cut down on unnecessary processing. That's why you only see one merged $match in the explain output instead of two separate ones—this is normal optimization behavior, not a bug.
2. Explain returns a document, not a cursor: When you chain .explain() before .aggregate(), the result is a BSON document containing the execution plan, not an iterable cursor. So calling cursor methods like hasNext() or next() on this result will throw an error, which is exactly what's supposed to happen.

How to view details for all aggregation pipeline stages #

To see the full breakdown of every stage in your pipeline (including $group and $sort), use one of these approaches:

Option 1: Use the explain option in aggregate()

Pass {explain: "<detail-level>"} as the second argument to aggregate(). Use "executionStats" for detailed execution metrics, or "allPlansExecution" to see all considered query plans:

db.restaurants.aggregate(
  [
    {$match: {"address.zipcode": {$in: ["10314", "11208", "11219"]}}},
    {$match: {"grades": {$elemMatch: {score: {$gte: 1}}}}},
    {$group: {_id: "$borough", count: {$sum: 1} }},
    {$sort: {count: -1} }
  ],
  {explain: "executionStats"}
)

In the returned document, check the executionStats.executionStages field—this will show you the full pipeline flow, including how the merged $match feeds into $group and $sort, along with metrics like document counts and execution times for each stage.

Option 2: Chain .explain() with a detail level

If you prefer the chained syntax, specify the detail level directly in .explain():

db.restaurants.explain("executionStats").aggregate([
  {$match: {"address.zipcode": {$in: ["10314", "11208", "11219"]}}},
  {$match: {"grades": {$elemMatch: {score: {$gte: 1}}}}},
  {$group: {_id: "$borough", count: {$sum: 1} }},
  {$sort: {count: -1} }
]);

This will return the same comprehensive execution plan as the first option, with all pipeline stages accounted for.

Quick note on cursors #

If you need an iterable cursor for the aggregation results (not the execution plan), just remove the .explain() call entirely:

const cursor = db.restaurants.aggregate([
  {$match: {"address.zipcode": {$in: ["10314", "11208", "11219"]}}},
  {$match: {"grades": {$elemMatch: {score: {$gte: 1}}}}},
  {$group: {_id: "$borough", count: {$sum: 1} }},
  {$sort: {count: -1} }
]);
// Now you can use cursor methods like cursor.hasNext() or cursor.next()

内容的提问来源于stack exchange，提问作者Pavel Bely