From 030eba4e3fa5bd51f20de3d77fd1f58d70b85814 Mon Sep 17 00:00:00 2001 From: Naomi Pentrel <5212232+npentrel@users.noreply.github.com> Date: Tue, 28 Sep 2021 15:42:15 +0200 Subject: [PATCH] DOCSP-18866 Geo indexing for time series --- source/core/timeseries/timeseries-limitations.txt | 6 +++++- source/release-notes/5.1.txt | 7 +++++++ 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/source/core/timeseries/timeseries-limitations.txt b/source/core/timeseries/timeseries-limitations.txt index 6043661232a..4e8c5186134 100644 --- a/source/core/timeseries/timeseries-limitations.txt +++ b/source/core/timeseries/timeseries-limitations.txt @@ -44,7 +44,11 @@ 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 ``metaField`` doesn't support the following index types: +In MongoDB 5.1, the ``metaField`` doesn't support :doc:`text +` indexes. + +In MongoDB 5.0, the ``metaField`` doesn't support the following index +types: - :doc:`2d ` - :doc:`2dsphere ` diff --git a/source/release-notes/5.1.txt b/source/release-notes/5.1.txt index 174421b6256..4fb46b4ccf5 100644 --- a/source/release-notes/5.1.txt +++ b/source/release-notes/5.1.txt @@ -80,6 +80,13 @@ If the new parameter the :ref:`query explain plan output `. +Geo Indexing for Time Series collections +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Starting in MongoDB 5.1, you can use :ref:`geo indexes +` on the ``metaField`` of time +series collections. + Schema Validation Errors Contain Description Field ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~