@@ -65,24 +65,24 @@ MongoDB 5.0 introduces the following aggregation operators:
65
65
- Description
66
66
67
67
* - :group:`$count`
68
- - :group:`$count (aggregation accumulator) <$count>`
68
+ - :group:`$count (aggregation accumulator) <$count>`
69
69
provides a count of all documents when used in the existing
70
70
pipeline :pipeline:`$group (aggregation) <$group>` stage and the
71
71
new MongoDB 5.0 :pipeline:`$setWindowFields` stage.
72
72
73
73
.. note:: Disambiguation
74
74
75
75
The :group:`$count (aggregation accumulator) <$count>` is
76
- distinct from the :pipeline:`$count (aggregation) <$count>`
77
- pipeline stage.
76
+ distinct from the :pipeline:`$count (aggregation) <$count>`
77
+ pipeline stage.
78
78
79
79
* - :expression:`$dateAdd`
80
80
- Increments a :doc:`Date </reference/method/Date>` object by a
81
81
specified number of time units.
82
82
83
83
* - :expression:`$dateDiff`
84
84
- Returns the difference between two dates.
85
-
85
+
86
86
* - :expression:`$dateSubtract`
87
87
- Decrements a :doc:`Date </reference/method/Date>` object by a
88
88
specified number of time units.
@@ -359,7 +359,7 @@ the ``"disabled"`` option.
359
359
``renameCollection`` Compatible with Sharded Collections
360
360
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
361
361
362
- Starting in MongoDB 5.0, you can use the :dbcommand:`renameCollection`
362
+ Starting in MongoDB 5.0, you can use the :dbcommand:`renameCollection`
363
363
command to change the name of a sharded collection.
364
364
365
365
.. _5.0-rel-notes-shell:
@@ -374,15 +374,15 @@ The ``mongo`` shell has been deprecated in MongoDB v5.0. The
374
374
replacement shell is :binary:`~bin.mongosh`. The legacy ``mongo`` shell
375
375
will be removed in a future release.
376
376
377
- Shell packaging also changes in MongoDB v5.0. Refer to the
377
+ Shell packaging also changes in MongoDB v5.0. Refer to the
378
378
:mongosh:`installation instructions </install>` for further details.
379
379
380
380
Shell Support for GCP and Azure KMS Providers
381
381
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
382
382
383
383
Starting in MongoDB 5.0 (and MongoDB 4.4.5), the Google Cloud Platform
384
384
KMS and Azure Key Vault are supported in both :binary:`~bin.mongosh`
385
- and the legacy :binary:`~bin.mongo` shell as
385
+ and the legacy :binary:`~bin.mongo` shell as
386
386
:ref:`Key Management Service (KMS) <field-level-encryption-kms>`
387
387
providers for :doc:`/core/security-client-side-encryption`.
388
388
@@ -442,12 +442,12 @@ Implicit Default Write Concern
442
442
Audit Events
443
443
~~~~~~~~~~~~
444
444
445
- Starting in MongoDB 5.0, ``startup`` and ``logout`` audit action types
446
- are available in
445
+ Starting in MongoDB 5.0, ``startup`` and ``logout`` audit action types
446
+ are available in
447
447
:doc:`System Event Audit Messages </reference/audit-message>`.
448
448
449
449
The ``dropCollection`` audit action type (``atype``) adds an audit
450
- event when a :ref:`view <3.4-reference-views>` is dropped.
450
+ event when a :ref:`view <3.4-reference-views>` is dropped.
451
451
452
452
``mongosShutdownTimeoutMillisForSignaledShutdown`` Parameter
453
453
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -460,10 +460,10 @@ complete before initiating a shutdown of :binary:`~bin.mongos`.
460
460
Configurable ``zstd`` Compression Level
461
461
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
462
462
463
- MongoDB 5.0 introduces the
463
+ MongoDB 5.0 introduces the
464
464
:setting:`~storage.wiredTiger.engineConfig.zstdCompressionLevel`
465
- configuration file option which allows for configurable compression
466
- levels when
465
+ configuration file option which allows for configurable compression
466
+ levels when
467
467
:setting:`~storage.wiredTiger.collectionConfig.blockCompressor` is set
468
468
to ``zstd``.
469
469
@@ -547,7 +547,7 @@ Previously, :dbcommand:`logRotate` would rotate the two logs together.
547
547
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
548
548
549
549
Starting in MongoDB 5.0, :ref:`slow operation
550
- <database-profiling-specify-slowms-threshold>` log messages include a
550
+ <database-profiling-specify-slowms-threshold>` log messages include a
551
551
``remote`` field specifying client IP address.
552
552
553
553
Define Variables Using the ``let`` Option
@@ -610,10 +610,11 @@ Aggregation Metrics
610
610
- :serverstatus:`metrics.commands.findAndModify.pipeline` *(Also available in 4.4.2+, 4.2.11+)*
611
611
- :serverstatus:`metrics.commands.findAndModify.arrayFilters` *(Also available in 4.4.2+, 4.2.11+)*
612
612
- :serverstatus:`metrics.dotsAndDollarsFields`
613
+ - :serverstatus:`metrics.operatorCounters`
613
614
614
615
Replication Metrics
615
616
- :serverstatus:`metrics.repl.reconfig.numAutoReconfigsForRemovalOfNewlyAddedFields`
616
-
617
+
617
618
Read Concern Counters
618
619
- :serverstatus:`readConcernCounters`, which reports on the
619
620
:ref:`read concern level <read-concern-levels>` specified by query
@@ -726,7 +727,7 @@ Upgrade Procedures
726
727
------------------
727
728
728
729
.. important:: Feature Compatibility Version
729
-
730
+
730
731
To upgrade to MongoDB 5.0 from a 4.4 deployment, the 4.4 deployment
731
732
must have ``featureCompatibilityVersion`` set to ``4.4``. To check
732
733
the version:
0 commit comments