@@ -240,19 +240,20 @@ The ``queryHash`` and ``planCacheKey`` are available in:
240
240
Index Filters
241
241
-------------
242
242
243
- Index filters determine which indexes the optimizer evaluates for a
244
- :term:`query shape`. A query shape consists of a combination of query,
245
- sort, and projection specifications. If an index filter exists for a
246
- given query shape, the optimizer only considers those indexes
247
- specified in the filter.
243
+ Index filters are set with the :dbcommand:`planCacheSetFilter` command
244
+ and determine which indexes the optimizer evaluates for a :term:`query
245
+ shape`. A query shape consists of a combination of query, sort, and
246
+ projection specifications. If an index filter exists for a given query
247
+ shape, the optimizer only considers those indexes specified in the
248
+ filter.
248
249
249
250
When an index filter exists for the query shape, MongoDB ignores the
250
251
:method:`~cursor.hint()`. To see whether MongoDB applied an index
251
252
filter for a query shape, check the :data:`~explain.queryPlanner.indexFilterSet`
252
253
field of either the :method:`db.collection.explain()` or the
253
254
:method:`cursor.explain()` method.
254
255
255
- Index filters only affects which indexes the optimizer evaluates; the
256
+ Index filters only affect which indexes the optimizer evaluates; the
256
257
optimizer may still select the collection scan as the winning plan for
257
258
a given query shape.
258
259
@@ -269,4 +270,4 @@ See :dbcommand:`planCacheListFilters`,
269
270
270
271
.. seealso::
271
272
272
- :doc:`/applications/indexes`
273
+ :doc:`/applications/indexes`
0 commit comments