DOCSP-52484: Restore driver server version mentions for v4.2+ (#13646)

* DOCSP-52484: Restore driver server version mentions for v4.2+

* Tech feedback

Author: mcmorisi

content/kotlin/upcoming/source/fundamentals/builders/aggregates.txt

@@ -870,12 +870,14 @@ Atlas Full-Text Search
 Use the ``search()`` method to create a :manual:`$search </reference/operator/aggregation/search/>`
 pipeline stage that specifies a full-text search of one or more fields.
 
-.. tip:: Only Available on Collections with an Atlas Search Index
+.. tip:: Only Available on Atlas for MongoDB v4.2 and later
 
-   This aggregation pipeline operator is only available for collections
-   with an :atlas:`Atlas search index </reference/atlas-search/index-definitions/>`.
-   Learn more about the required setup and the functionality of this operator
-   from the :ref:`Atlas Search <fts-top-ref>` documentation.
+   This aggregation pipeline operator is only available for collections hosted
+   on :atlas:`MongoDB Atlas </>` clusters running v4.2 or later that are covered
+   by an :atlas:`Atlas search index
+   </reference/atlas-search/index-definitions/>`. Learn more about the required
+   setup and the functionality of this operator from the :ref:`Atlas Search
+   <fts-top-ref>` documentation.
 
 The following example creates a pipeline stage that searches the ``title``
 field in the ``movies`` collection for text that contains the word "Future":
@@ -919,6 +921,13 @@ Use the ``searchMeta()`` method to create a
 pipeline stage which returns only the metadata part of the results from
 Atlas full-text search queries.
 
+.. tip:: Only Available on MongoDB Atlas v4.4.11 and later
+
+   This aggregation pipeline operator is only available
+   for :atlas:`MongoDB Atlas </>` clusters running v4.4.11 and later. For a
+   detailed list of version availability, see the MongoDB Atlas documentation
+   on :atlas:`$searchMeta </atlas-search/aggregation-stages/searchMeta>`.
+
 The following example shows the ``count`` metadata for an Atlas search
 aggregation stage:
 

content/kotlin/upcoming/source/fundamentals/builders/projections.txt

@@ -230,6 +230,12 @@ When you've specified matching criteria in the **query** portion of your operati
 variant to specify a :manual:`positional projection </reference/operator/projection/positional/#sorts-and-the-positional-operator>` to include
 the first element of an array. Only documents that match the query filter will be retrieved.
 
+.. important::
+
+   In MongoDB versions earlier than 4.4, the specified array field must appear in
+   the query filter. Beginning in MongoDB 4.4, you can use a positional project
+   on an array field that does not appear in the query filter.
+
 The following example projects the first element of the ``temperatures`` array:
 
 .. io-code-block::

content/kotlin/upcoming/source/fundamentals/connection/network-compression.txt

@@ -19,7 +19,7 @@ The driver supports the following algorithms:
 
 1. `Snappy <https://google.github.io/snappy/>`__
 #. `Zlib <https://zlib.net/>`__
-#. `Zstandard <https://github.com/facebook/zstd/>`__
+#. `Zstandard <https://github.com/facebook/zstd/>`__: available in MongoDB 4.2 and later
 
 The driver tests against the following versions of these libraries:
 

content/kotlin/upcoming/source/fundamentals/crud/read-operations/sort.txt

@@ -320,9 +320,9 @@ The data is modeled with the following Kotlin data class:
       OrderScore(id=5, description=one large vanilla and chocolate cake, score=0.6)
       OrderScore(id=2, description=two medium vanilla birthday cakes, score=0.6)
 
-.. note:: Text Search Behavior in MongoDB 6.0 or Later
+.. note:: Text Search Behavior in MongoDB 4.4 or Later
 
-   The structure of text search has changed for MongoDB 6.0 or later. You no
+   The structure of text search has changed for MongoDB 4.4 or later. You no
    longer need to project ``Projections.metaTextScore()`` into your
    ``FindFlow`` instance in order to sort on the text score. In addition,
    the field name you specify in a ``$meta`` text score aggregation operation

content/kotlin/upcoming/source/fundamentals/indexes.txt

@@ -97,9 +97,11 @@ your application uses indexes:
 - Avoid adding indexes that you infrequently use. Note that when a write
   operation updates an indexed field, MongoDB updates the related index.
 
-Since MongoDB supports dynamic schemas, applications can query against fields whose names cannot be known in advance or
-are arbitrary with :manual:`wildcard indexes </core/index-wildcard/>`. Wildcard indexes are 
-not designed to replace workload-based index planning.
+Since MongoDB supports dynamic schemas, applications can query against fields
+whose names cannot be known in advance or are arbitrary. MongoDB 4.2 introduced
+:manual:`wildcard indexes </core/index-wildcard/>` to help support these
+queries. Wildcard indexes are not designed to replace workload-based index
+planning.
 
 For more information on designing your data model and choosing indexes appropriate for your application, see the MongoDB
 server documentation on :manual:`Indexing Strategies </applications/indexes>` and
@@ -587,7 +589,7 @@ The following snippet removes the "title_text" index from the collection:
 Remove an Index Using a Wildcard Character
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-You can drop all indexes by calling the
+Starting with MongoDB 4.2, you can drop all indexes by calling the
 ``dropIndexes()`` method on your collection:
 
 .. literalinclude:: /examples/generated/IndexesTest.snippet.drop-all-indexes.kt

content/kotlin/upcoming/source/fundamentals/stable-api.txt

@@ -14,6 +14,13 @@
    :depth: 1
    :class: singlecol
 
+.. note::
+
+   The {+stable-api+} feature requires MongoDB Server 5.0 or later.
+
+   You should only use the {+stable-api+} feature if all the MongoDB
+   servers you are connecting to support this feature.
+
 Overview
 --------
 

content/kotlin/upcoming/source/fundamentals/time-series.txt

@@ -53,6 +53,10 @@ method:
 .. literalinclude:: /examples/generated/TimeSeriesTest.snippet.create-time-series-collection.kt
    :language: kotlin
 
+.. important::
+
+   Versions earlier than MongoDB 5.0 cannot create a time series collection.
+
 To check if you successfully created the collection, send the
 ``"listCollections"`` command to the `runCommand() <{+driver-api+}/-mongo-database/run-command.html>`__ method.
 
@@ -89,8 +93,9 @@ and :ref:`aggregating data <kotlin-aggregation>`.
 
 .. note:: Window Functions
 
-   You can use window functions to perform operations on a
-   contiguous span of time series data.
+   MongoDB version 5.0 introduces window functions into the aggregation
+   pipeline. You can use window functions to perform operations on a contiguous
+   span of time series data.
 
 For more information, see our
 :ref:`Aggregates Builders guide <builders-aggregates-setWindowFields>`.

content/kotlin/upcoming/source/includes/mongodb-compatibility-table-kotlin.rst

@@ -7,13 +7,19 @@
      - MongoDB 8.0
      - MongoDB 7.0
      - MongoDB 6.0
+     - MongoDB 5.0
+     - MongoDB 4.2
 
    * - 5.2 to 5.5
      - ✓
      - ✓
      - ✓
+     - ✓
+     - ✓
 
    * - 4.10 to 5.1
      - ⊛
      - ✓
      - ✓
+     - ✓
+     - ✓

content/kotlin/upcoming/source/usage-examples/count.txt

@@ -36,6 +36,15 @@ When you call the ``countDocuments()`` method, you can optionally pass a
 **query filter** parameter. You cannot pass any parameters when you call
 ``estimatedDocumentCount()``.
 
+.. important:: Stable API V1 and MongoDB Server Issue
+
+   If you are using the {+stable-api+} ``v1`` with the "strict" option and a 
+   MongoDB server version between 5.0.0 and 5.0.8 inclusive, method calls to
+   ``estimatedDocumentCount()`` may error due to a server bug. 
+
+   Upgrade to MongoDB server 5.0.9 or later, or set the {+stable-api+} "strict" option to 
+   ``false`` to avoid this issue.
+
 You can also pass an optional parameter to either of these methods to
 specify the behavior of the call: