DOCSP-21019-revert-time-series-and-indexes-updates (#688)

* DOCSP-21019-revert-time-series-and-indexes-updates

* DOCSP-21019-revert-time-series-and-indexes-updates

Co-authored-by: jason-price-mongodb <[email protected]>

Author: jason-price-mongodb

source/core/timeseries/timeseries-limitations.txt

@@ -59,79 +59,14 @@ To remove all documents from a collection, use the
 
 .. _timeseries-limitations-secondary-indexes:
 
-Time Series Secondary Indexes
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Secondary Indexes
+~~~~~~~~~~~~~~~~~
 
 You can add :term:`secondary indexes <secondary index>` on the fields
 specified as the ``timeField`` and the ``metaField``. If the field value
 for the ``metaField`` field is a document, you can also create secondary
 indexes on fields inside that document.
 
-The following sections describe:
-
-- Additional secondary indexes you can add.
-
-- Secondary index limitations.
-
-Time Series Secondary Indexes in MongoDB 5.3
-````````````````````````````````````````````
-
-Starting in MongoDB 5.3:
-
-- You can add the following secondary indexes to a :ref:`time series
-  collection <manual-timeseries-collection>`:
-  
-  - :doc:`Partial
-    </core/index-partial>`, :doc:`2d </core/2d>`, and :doc:`2dsphere
-    </core/2dsphere>` indexes to a metadata field. 
-
-  - :doc:`2dsphere </core/2dsphere>` and :doc:`partial
-    </core/index-partial>` indexes to a measurement field.
-
-  - :doc:`Compound index </core/index-compound>` on time, metadata, or
-    measurement fields.
-
-- If you need to downgrade the Feature Compatibility Version (FCV), 
-  you must first drop any indexes that are incompatible with the
-  downgraded FCV. See :dbcommand:`setFeatureCompatibilityVersion`.
-
-- You can use the :query:`$or`, :query:`$in`, and :query:`$geoWithin`
-  operators with :doc:`partial indexes </core/index-partial>` on a time
-  series collection.
-
-- You can use the :pipeline:`$geoNear` pipeline operator with a:
-
-  .. include:: /includes/geoNear-time-series.rst
-
-For example, the following ``sensorData`` collection contains
-temperature readings:
-
-.. code-block:: javascript
-
-   db.sensorData.insertMany( [
-      {
-         "metadata": { "sensorId": 5578, "type": "temperature" },
-         "timestamp": ISODate("2022-01-15T00:00:00.000Z"),
-         "temperatureReading": 12
-      },
-      {
-         "metadata": { "sensorId": 5578, "type": "temperature" },
-         "timestamp": ISODate("2022-01-15T04:00:00.000Z"),
-         "temperatureReading": 11
-      }
-   ] )
-
-The following example creates an ascending secondary index on the
-``metadata.sensorId`` and ``temperatureReading`` fields in the
-``sensorData`` collection:
-
-.. code-block:: javascript
-
-   db.sensorData.createIndex( { "metadata.sensorId": 1, "temperatureReading": 1 } )
-
-Secondary Index Limitations
-```````````````````````````
-
 In MongoDB 5.1, the ``metaField`` doesn't support :doc:`text
 </core/index-text>` indexes.
 

source/release-notes/5.3.txt

@@ -57,19 +57,6 @@ MongoDB 5.3 introduces the following aggregation operators:
 General Improvements
 --------------------
 
-Time Series Collection Improvements
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Starting in MongoDB 5.3, you can:
-
-- Add additional :term:`secondary index <secondary index>` types to
-  :ref:`time series collections <manual-timeseries-collection>`. See
-  :ref:`timeseries-limitations-secondary-indexes`.
-
-- Use the :pipeline:`$geoNear` pipeline operator with a:
-
-  .. include:: /includes/geoNear-time-series.rst
-
 ``serverStatus`` Output Change
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~