Skip to content

Commit ea845c6

Browse files
authored
DOCSP-41298-Geospatial-indexes-covering (#8325) (#8479)
* DOCSP-41298-Geospatial-indexes-covering * Reverting an edit. * Responding to internal feedback, minor edit. * Responding to external feedback, removing irrelevant link, small edit. (cherry picked from commit 1cff141)
1 parent 1f9133a commit ea845c6

File tree

3 files changed

+8
-14
lines changed

3 files changed

+8
-14
lines changed

source/core/indexes/index-types/index-geospatial.txt

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -51,10 +51,6 @@ on the ``location`` field. After creating the index, you can query
5151
using the :query:`$near` operator to return a list of nearby stations,
5252
sorted from nearest to farthest.
5353

54-
Indexing commonly queried fields increases the chances of :ref:`covering <indexes-covered-queries>` those queries. Covered queries
55-
are queries that can be satisfied entirely using an index, without
56-
examining any documents. This optimizes query performance.
57-
5854
Get Started
5955
-----------
6056

source/core/query-optimization.txt

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -92,10 +92,9 @@ index use <regex-index-use>`.
9292
Covered Query
9393
-------------
9494

95-
A covered query is a query that can be satisfied entirely using an index
96-
and does not have to examine any documents. An index
97-
:ref:`covers <indexes-covered-queries>` a query when all of the
98-
following apply:
95+
A covered query is a query that can be satisfied entirely using an
96+
index and does not have to examine any documents. An index covers a
97+
query when all of the following apply:
9998

10099
- all the fields in the :ref:`query <read-operations-query-document>`
101100
are part of an index, **and**
@@ -205,8 +204,6 @@ To determine whether a query is a covered query, use the
205204
:method:`db.collection.explain()` or the :method:`~cursor.explain()`
206205
method and review the :ref:`results <explain-output-covered-queries>`.
207206

208-
For more information see :ref:`indexes-measuring-use`.
209-
210207
.. toctree::
211208
:titlesonly:
212209
:hidden:

source/reference/explain-results.txt

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -941,10 +941,11 @@ For more information on execution statistics of collection scans, see
941941
Covered Queries
942942
---------------
943943

944-
When an index covers a query, MongoDB can both match the query
945-
conditions **and** return the results using only the index keys; i.e.
946-
MongoDB does not need to examine documents from the collection to
947-
return the results.
944+
When an index :ref:`covers <indexes-covered-queries>` a query,
945+
MongoDB can both match the query conditions **and** return the
946+
results using only the index keys. MongoDB does not need to
947+
examine documents from the collection to to perform any part of the
948+
query.
948949

949950
When an index covers a query, the explain result has an ``IXSCAN``
950951
stage that is **not** a descendant of a ``FETCH`` stage, and in the

0 commit comments

Comments
 (0)