Skip to content

Commit b07a592

Browse files
authored
DOCS-15063 Replace old query optimizer language (#2379)
* DOCS-15063 replace old optimizer language * replace more references to optimizer
1 parent a550e64 commit b07a592

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

source/core/query-plans.txt

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Query Plans
1616

1717
.. TODO Consider moving this to the mechanics of the index section
1818

19-
For a query, the MongoDB query optimizer chooses and caches the most
19+
For a query, the MongoDB query planner chooses and caches the most
2020
efficient query plan given the available indexes. The evaluation of the
2121
most efficient query plan is based on the number of "work units"
2222
(``works``) performed by the query execution plan when the query planner
@@ -237,10 +237,10 @@ Index Filters
237237
-------------
238238

239239
Index filters are set with the :dbcommand:`planCacheSetFilter` command
240-
and determine which indexes the optimizer evaluates for a :term:`query
240+
and determine which indexes the planner evaluates for a :term:`query
241241
shape`. A query shape consists of a combination of query, sort, and
242242
projection specifications. If an index filter exists for a given query
243-
shape, the optimizer only considers those indexes specified in the
243+
shape, the planner only considers those indexes specified in the
244244
filter.
245245

246246
When an index filter exists for the query shape, MongoDB ignores the
@@ -249,15 +249,15 @@ filter for a query shape, check the :data:`~explain.queryPlanner.indexFilterSet`
249249
field of either the :method:`db.collection.explain()` or the
250250
:method:`cursor.explain()` method.
251251

252-
Index filters only affect which indexes the optimizer evaluates; the
253-
optimizer may still select the collection scan as the winning plan for
252+
Index filters only affect which indexes the planner evaluates; the
253+
planner may still select the collection scan as the winning plan for
254254
a given query shape.
255255

256256
Index filters exist for the duration of the server process and do not
257257
persist after shutdown. MongoDB also provides a command to manually remove
258258
filters.
259259

260-
Because index filters override the expected behavior of the optimizer
260+
Because index filters override the expected behavior of the planner
261261
as well as the :method:`~cursor.hint()` method, use index filters
262262
sparingly.
263263

0 commit comments

Comments
 (0)