AWS Security ChangesHomeSearch

AWS documentdb: Document plan cache filters support in Planner version 3

Service: documentdb · 2026-09-29 · Documentation low

File: documentdb/latest/devguide/query-planner-v3.md

Summary

Adds a new "Plan cache filters" section and TOC entry explaining that Planner version 3.0 supports plan cache filters (index filters) to restrict the indexes the planner considers per query shape, and lists which commands (distinct, aggregate, $lookup/$graphLookup foreign collections) support them, with a link to the plan-cache-filter reference page.

Security assessment

The change is purely about query-planner performance tuning (index selection for a query shape) and contains no authentication, authorization, encryption, or exposure content; index filters affect plan choice, not access control.

Evidence

+Planner version 3.0 supports plan cache filters, also called index filters, which let you restrict the set of indexes that the planner considers for a specific query shape.

Diff

diff --git a/documentdb/latest/devguide/query-planner-v3.md b/documentdb/latest/devguide/query-planner-v3.md
index e3d7fe978..824180618 100644
--- a//documentdb/latest/devguide/query-planner-v3.md
+++ b//documentdb/latest/devguide/query-planner-v3.md
@@ -7 +7 @@
-PrerequisitesSelecting planner version 3.0 as the default query plannerBest practicesLimitationsImprovements to aggregate and distinct OperatorsPotential behavior differences between planner version 1.0, 3.0, and MongoDB
+PrerequisitesSelecting planner version 3.0 as the default query plannerBest practicesLimitationsImprovements to aggregate and distinct OperatorsPlan cache filtersPotential behavior differences between planner version 1.0, 3.0, and MongoDB
@@ -24,0 +25,2 @@ Planner Version 3 in Amazon DocumentDB 8.0 supports 21 aggregation stages, inclu
+  * Plan cache filters
+
@@ -137,0 +140,17 @@ Planner version 3.0 introduces improvements across $aggregate stages, and $disti
+## Plan cache filters
+
+Planner version 3.0 supports plan cache filters, also called index filters, which let you restrict the set of indexes that the planner considers for a specific query shape. Filters are set with a database command and applied on the server, so if you experience a query regression you can mitigate it without modifying your application code.
+
+Planner version 3.0 applies plan cache filters to more commands than planner version 2.0 does:
+
+  * The `distinct` command requires planner version 3.0.
+
+  * The `aggregate` command requires planner version 3.0 and Amazon DocumentDB 8.0.2. A filter applies when the pipeline reads the collection through a leading `$match` stage.
+
+  * A filter set on the foreign collection of a `$lookup` or `$graphLookup` stage drives the index used to scan that foreign collection. This also requires planner version 3.0 and Amazon DocumentDB 8.0.2.
+
+
+
+
+For more information about the command reference, supported query shapes, worked examples, and how filters interact with hints, see [Plan cache filters](./plan-cache-filter.html).
+