Skip to content

DOCSP-17695 update known issues 5.0.1 #5596

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 18 additions & 20 deletions source/core/timeseries/timeseries-granularity.txt
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,10 @@ Set Granularity for Time Series Data

.. note::

Currently, you can only set a collection's ``granularity`` parameter
when creating the collection. After creation the parameter can't be
modified. See :ref:`known issues <5.0-known-issue-granularity>`.
You must be running MongoDB 5.0.1 or later in order to change a
time series collection's granularity after the collection has been
created. See :ref:`MongoDB 5.0 known issues
<5.0-known-issue-granularity>`.

When you create a :ref:`time series collection
<manual-timeseries-collection>`, set the granularity to the value that
Expand Down Expand Up @@ -124,24 +125,21 @@ which contains the ``options.timeseries.granularity`` field.
}
}

.. TODO: uncomment once SERVER-58171 is fixed
Change the ``granularity`` of a Time Series Collection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

.. Change the ``granularity`` of a Time Series Collection
.. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To change the ``granularity`` parameter value, issue the following
:dbcommand:`collMod` command:

.. code-block:: javascript

.. To change the ``granularity`` parameter value, issue the following
.. :dbcommand:`collMod` command:

.. .. code-block:: javascript

.. db.runCommand({
.. collMod: "weather24h",
.. timeseries: { granularity: "hours" }
.. })
db.runCommand({
collMod: "weather24h",
timeseries: { granularity: "hours" }
})

.. Once the ``granularity`` is set it can only be increased by one level at
.. a time. From ``"seconds"`` to ``"minutes"`` or from ``"minutes"`` to
.. ``"hours"``. Other changes are not allowed. If you need to change the
.. ``granularity`` from ``"seconds"`` to ``"hours"``, first increase the
.. ``granularity`` to ``"minutes"`` and then to ``"hours"``.
Once the ``granularity`` is set it can only be increased by one level at
a time. From ``"seconds"`` to ``"minutes"`` or from ``"minutes"`` to
``"hours"``. Other changes are not allowed. If you need to change the
``granularity`` from ``"seconds"`` to ``"hours"``, first increase the
``granularity`` to ``"minutes"`` and then to ``"hours"``.
23 changes: 5 additions & 18 deletions source/core/timeseries/timeseries-limitations.txt
Original file line number Diff line number Diff line change
Expand Up @@ -94,24 +94,11 @@ can't be modified.
Modification of ``granularity``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Currently, you can only set a collection's ``granularity`` parameter
when creating the collection. After creation the parameter can't be
modified.

.. note::

See :ref:`known issues <5.0-known-issue-granularity>`.

.. TODO: use below copy once SERVER-58171 is fixed

.. Modification of ``granularity``
.. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

.. Once the ``granularity`` is set it can only be increased by one level at
.. a time. From ``"seconds"`` to ``"minutes"`` or from ``"minutes"`` to
.. ``"hours"``. Other changes are not allowed. If you need to change the
.. ``granularity`` from ``"seconds"`` to ``"hours"``, first increase the
.. ``granularity`` to ``"minutes"`` and then to ``"hours"``.
Once the ``granularity`` is set it can only be increased by one level at
a time. From ``"seconds"`` to ``"minutes"`` or from ``"minutes"`` to
``"hours"``. Other changes are not allowed. If you need to change the
``granularity`` from ``"seconds"`` to ``"hours"``, first increase the
``granularity`` to ``"minutes"`` and then to ``"hours"``.

Schema Validation
~~~~~~~~~~~~~~~~~
Expand Down
47 changes: 23 additions & 24 deletions source/release-notes/5.0.txt
Original file line number Diff line number Diff line change
Expand Up @@ -41,11 +41,11 @@ Issues fixed:
Time Series Collections
-----------------------

MongoDB 5.0 introduces :term:`time series collections <time series
collection>` which efficiently store sequences of measurements over a
period of time. Compared to normal collections, storing time series data
in time series collections improves query efficiency and reduces disk
usage for your data and indexes.
MongoDB 5.0 introduces :ref:`time series collections
<manual-timeseries-collection>` which efficiently store sequences of
measurements over a period of time. Compared to normal collections,
storing time series data in time series collections improves query
efficiency and reduces disk usage for your data and indexes.

Aggregation
-----------
Expand Down Expand Up @@ -760,34 +760,33 @@ To download MongoDB 5.0, go to the `MongoDB Download Center
- `All Third Party License Notices <https://github.com/mongodb/mongo/blob/v4.4/distsrc/THIRD-PARTY-NOTICES>`_.

.. _5.0-known-issues:
.. _5.0-known-issue-granularity:
.. _5.0-known-issue-backup-resharding:

Known Issues
------------

.. _5.0-known-issue-granularity:
.. list-table::
:header-rows: 1
:widths: 15 70 20

* - In Version
- Issues
- Status

Modification of ``granularity`` for Time Series Collections
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* - 5.0.0

Currently, you can only set a collection's ``granularity`` parameter
when creating the collection. After creation the parameter can't be
modified. Once :issue:`SERVER-58171` is resolved, you will be able to
modify the ``granularity`` of a
:ref:`time series collection <manual-timeseries-collection>` after
creation. :issue:`SERVER-58171` is expected to be resolved in MongoDB
5.0.1.
- :issue:`SERVER-58171`: A Time Series collection's ``granularity``
parameter cannot be modified after the collection is created.

.. _5.0-known-issue-backup-resharding:
- Fixed in 5.0.1

* - 5.0.0

Backup and Restore Not Supported During Resharding Operations
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- :issue:`SERVER-58392`: An ongoing resharding operation may
prevent a backup or restore operation from succeeding.

Currently, a resharding operation may pin timestamps in the storage
engine in a manner that prevents a restore operation from proceeding.
Once :issue:`SERVER-58392` is resolved, you will be able to backup and
restore your collection while a resharding operation occurs.
:issue:`SERVER-58392` is expected to be resolved in a patch release of
MongoDB 5.0.
- Unresolved

Report an Issue
---------------
Expand Down