MongoDB两阶段聚合返回空结果：如何定位数据丢失环节？

Great question! When you run a two-stage pipeline like this and end up with an empty result set, MongoDB doesn’t natively tell you which stage ($match or $redact) is responsible. You’ll need to do a bit of targeted testing to narrow it down. Here’s how to approach it:

1. Isolate the $match Stage First #

The simplest way to start is to run only the $match stage and check if it returns any documents.

Run this pipeline:

db.thingies.aggregate([ { $match: { SOME_CONDITION } } ])

• If this returns documents: The empty result from your full pipeline is definitely caused by the $redact stage pruning all matching documents.
• If this returns nothing: The $match stage didn’t find any documents to begin with—so you’re looking at a 404-style "not found" scenario.

2. Use $facet to Compare Stage Results Side-by-Side #

If you want to validate both stages in a single query (instead of running two separate pipelines), use the $facet stage to run parallel branches:

db.thingies.aggregate([
  { $match: { SOME_CONDITION } },
  {
    $facet: {
      documents_after_match: [ { $addFields: { stage: "post-match" } } ],
      documents_after_redact: [ 
        { $redact: { $cond: { if: { SOME_PERMISSION_CHECK }, then: "$$KEEP", else: "$$PRUNE" } } },
        { $addFields: { stage: "post-redact" } }
      ]
    }
  }
])

This will return an object with two arrays:

• documents_after_match: All documents that passed the $match stage.
• documents_after_redact: Only the documents that passed both $match and $redact.

Compare the lengths of these arrays:

• If documents_after_match has entries but documents_after_redact is empty: $redact pruned everything.
• If documents_after_match is empty: $match failed to find any documents.

3. Modify $redact to Flag (Instead of Prune) Unauthorized Documents #

If you need to see exactly which documents were filtered out by $redact (instead of just knowing they were), temporarily adjust your $redact logic to keep unauthorized documents but mark them explicitly:

db.thingies.aggregate([
  { $match: { SOME_CONDITION } },
  {
    $redact: {
      $cond: {
        if: { SOME_PERMISSION_CHECK },
        then: "$$KEEP",
        else: { $mergeObjects: [ "$$CURRENT", { _permission_denied: true } ] }
      }
    }
  }
])

Instead of pruning documents that fail the permission check, this adds an _permission_denied: true field to them. Now you can:

• See all documents that passed $match (including those that would have been pruned).
• Count how many were flagged as unauthorized vs. kept.

How to Identify Which Stage Removed the "Last" Document #

This ties directly into the methods above:

• If you run the isolated $match stage and get zero documents: The last (and only) potential documents were removed by $match.
• If $match returns documents, but the modified $redact pipeline shows all of them have _permission_denied: true: The last documents were pruned by $redact.
• Using $facet, you can even see the exact list of documents that made it past $match but not $redact by comparing the two arrays.

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