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