DOCSP-26661 EOL cleanup for Index pages. (#2189) (#2200)

* DOCSP-26661 Fixes references to EOL releases for index pages in source/code

* Fixes EOL version on Query Optimization page

* EOL cleanup on multikey, sparse, and multikey bounds pages

* EOL fixes to index pages

* Removes version reference from include

* Removes text index table

* Removes text index table

Author: kennethdyer

source/core/index-multikey.txt

@@ -39,12 +39,11 @@ To create a multikey index, use the
 MongoDB automatically creates a multikey index if any indexed field is
 an array; you do not need to explicitly specify the multikey type.
 
-.. versionchanged:: 3.4
+.. note:: 
 
    *For the WiredTiger and In-Memory storage engines only*,
 
-   Starting in MongoDB 3.4, for multikey indexes created using MongoDB
-   3.4 or later, MongoDB keeps track of which indexed field or fields
+   For multikey indexes, MongoDB keeps track of which indexed field or fields
    cause an index to be a multikey index. Tracking this information
    allows the MongoDB query engine to use tighter index bounds.
 
@@ -158,13 +157,8 @@ Covered Queries
 
 .. include:: /includes/fact-multikey-index-covered-query.rst
 
-However, starting in 3.6, multikey indexes can cover queries over the
-non-array fields if the index tracks which field or fields cause the
-index to be multikey. Multikey indexes created in MongoDB 3.4 or later
-on storage engines other than MMAPv1 [#]_ track this data.
-
-.. [#]
-   Starting in version 4.2, MongoDB removes the deprecated MMAPv1 storage engine.
+Multikey indexes can cover queries over non-array fields if the index tracks 
+which field or fields cause the index to be multikey. 
 
 Query on the Array Field as a Whole
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -211,20 +205,6 @@ $expr
 
 :query:`$expr` does not support multikey indexes.
 
-Indexes Built on MongoDB 3.2 or Earlier
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Indexes built on MongoDB 3.2 or earlier do not contain the necessary
-flags to support optimized multikey index use. To benefit from the
-performance enhancements of multikey indexes, you must either:
-
-- Rebuild the older-format indexes on MongoDB 3.4 or later. See
-  :method:`db.collection.reIndex()`.
-
-- On a replica set, :doc:`resync the replica set members
-  </tutorial/resync-replica-set-member/>` containing older-format
-  indexes.
-
 Examples
 --------
 

source/core/index-sparse.txt

@@ -23,13 +23,10 @@ field.
 
 .. important::
 
-   .. versionchanged:: 3.2 
-   
-      Starting in MongoDB 3.2, MongoDB provides the option to create
-      :ref:`partial indexes <index-type-partial>`. Partial indexes
-      offer a superset of the functionality of sparse indexes. If you
-      are using MongoDB 3.2 or later, :ref:`partial indexes
-      <index-type-partial>` should be preferred over sparse indexes.
+   MongoDB provides the option to create
+   :ref:`partial indexes <index-type-partial>`. Partial indexes
+   offer a superset of the functionality of sparse indexes.
+   Partial Indexes should be preferred over sparse indexes.
 
 Create a Sparse Index
 ---------------------
@@ -70,8 +67,6 @@ sparse index on the ``x`` field unless explicitly hinted. See
 :ref:`sparse-index-incomplete-results` for an example that details the
 behavior.
 
-.. versionchanged:: 3.4
-
 .. include:: /includes/fact-sparse-index-hint-count.rst
 
 Indexes that are ``sparse`` by Default

source/core/index-text.txt

@@ -22,33 +22,11 @@ Overview
 Versions
 --------
 
-.. list-table::
-   :header-rows: 1
-   :widths: 30 70
+The text index is available in three versions.  By default, MongoDB uses
+version 3 with new text indexes.
 
-   * - ``text`` Index Version
-     - Description
-
-   * - Version 3
-
-     - MongoDB introduces a version 3 of the ``text`` index. Version 3
-       is the default version of ``text`` indexes created in
-       MongoDB 3.2 and later.
-
-   * - Version 2
-
-     - MongoDB 2.6 introduces a version 2 of the ``text`` index.
-       Version 2 is the default version of ``text`` indexes created
-       in MongoDB 2.6 and 3.0 series.
-
-   * - Version 1
-
-     - MongoDB 2.4 introduces a version 1 of the ``text`` index.
-       MongoDB 2.4 can only support version ``1``.
-
-To override the default version and specify a different version,
-include the option ``{ "textIndexVersion": <version> }`` when
-creating the index.
+To override the default and use an older version, use the ``textIndexVersion`` 
+option when you create the index.
 
 .. _create-text-index:
 
@@ -154,8 +132,6 @@ indexes, see :ref:`Compound Text Indexes <text-index-compound>`.
 Case Insensitivity
 ------------------
 
-.. versionchanged:: 3.2
-
 The version 3 ``text`` index supports the common ``C``, simple ``S``,
 and for Turkish languages, the special ``T`` case foldings as specified
 in `Unicode 8.0 Character Database Case Folding
@@ -180,8 +156,6 @@ text index treat them as distinct.
 Diacritic Insensitivity
 -----------------------
 
-.. versionchanged:: 3.2
-
 With version 3, ``text`` index is diacritic insensitive. That is, the
 index does not distinguish between characters that contain diacritical
 marks and their non-marked counterpart, such as ``é``, ``ê``, and
@@ -202,8 +176,6 @@ diacritics as distinct.
 Tokenization Delimiters
 -----------------------
 
-.. versionchanged:: 3.2
-
 For tokenization, version 3 ``text`` index uses the delimiters
 categorized under ``Dash``, ``Hyphen``, ``Pattern_Syntax``,
 ``Quotation_Mark``, ``Terminal_Punctuation``, and ``White_Space`` in

source/core/multikey-index-bounds.txt

@@ -152,14 +152,11 @@ MongoDB can compound the two bounds to use the combined bounds of:
 Range Queries on a Scalar Indexed Field (WiredTiger)
 ````````````````````````````````````````````````````
 
-.. versionchanged:: 3.4
+*For the WiredTiger and In-Memory storage engines only*, 
 
-   *For the WiredTiger and In-Memory storage engines only*, 
-
-   Starting in MongoDB 3.4, for multikey indexes created using MongoDB
-   3.4 or later, MongoDB keeps track of which indexed field or fields cause an
-   index to be a multikey index. Tracking this information allows the
-   MongoDB query engine to use tighter index bounds.
+In multikey index, MongoDB keeps track of which indexed field or fields 
+cause an index to be a multikey index. Tracking this information allows the
+MongoDB query engine to use tighter index bounds.
 
 The aforementioned :ref:`compound index <index-type-compound>` is on
 the scalar field [#scalar]_ ``item`` and the array field ``ratings``:
@@ -170,8 +167,7 @@ the scalar field [#scalar]_ ``item`` and the array field ``ratings``:
 
 For the WiredTiger and the In-Memory storage engines, if a query
 operation specifies multiple predicates on the indexed scalar field(s)
-of a compound multikey index created in MongoDB 3.4 or later, MongoDB
-will intersect the bounds for the field.
+of a compound multikey index, MongoDB will intersect the bounds for the field.
 
 For example, the following operation specifies a range query on the
 scalar field as well as a range query on the array field:

source/core/query-optimization.txt

@@ -9,7 +9,7 @@ Query Optimization
 .. contents:: On this page
    :local:
    :backlinks: none
-   :depth: 1
+   :depth: 2
    :class: singlecol
 
 Indexes improve the efficiency of read operations by reducing the
@@ -126,9 +126,10 @@ For the specified index to cover the query, the projection document
 must explicitly specify ``_id: 0`` to exclude the ``_id`` field from
 the result since the index does not include the ``_id`` field.
 
-.. versionchanged:: 3.6
-   An index can cover a query on fields within embedded documents.
-   [#index-embedded-document-fields]_
+Embedded Documents
+~~~~~~~~~~~~~~~~~~
+
+An index can cover a query on fields within embedded documents.
 
 For example, consider a collection ``userdata`` with documents of the
 following form:
@@ -149,18 +150,17 @@ The ``{ "user.login": 1 }`` index will cover the query below:
 
    db.userdata.find( { "user.login": "tester" }, { "user.login": 1, _id: 0 } )
 
-.. [#index-embedded-document-fields] To index fields
-   in embedded documents, use :term:`dot notation`.
+.. note::
+
+   To index fields in embedded documents, use :term:`dot notation`.
 
 .. _multikey-covering:
 
 Multikey Covering
 ~~~~~~~~~~~~~~~~~
 
-Starting in 3.6, multikey indexes can cover queries over the non-array fields
+Multikey indexes can cover queries over the non-array fields
 if the index tracks which field or fields cause the index to be multikey.
-Multikey indexes created in MongoDB 3.4 or later on storage engines other
-than MMAPv1 track this data.
 
 .. include:: /includes/fact-multikey-index-covered-query.rst
 

source/includes/extracts-parent-fact-covered-query-sharded-collection.yaml

@@ -1,16 +1,8 @@
 ref: _fact-covered-query-sharded-collection
 content: |
 
-  .. FYI -- we doc this in the negative since this is included
-  .. in the limitation/restriction section.
-  .. We probably could word this in "can only cover ..."
-  .. to make it more positive.
+  When run on :program:`mongos`, indexes can only {{cover}} queries on 
+  :term:`sharded <shard>` collections if the index contains
+  the shard key.
 
-  Starting in MongoDB 3.0, an index cannot {{cover}} a query on a
-  :term:`sharded <shard>` collection when run against a
-  :binary:`~bin.mongos` if the index does not contain the shard key.
-
-  In previous versions, an index cannot :ref:`cover <covered-queries>`
-  a query on a :term:`sharded <shard>` collection when run against a
-  :binary:`~bin.mongos`.
 ...