@@ -387,9 +387,19 @@ General Aggregation Improvements
387
387
``$out``
388
388
````````
389
389
390
- Starting in MongoDB 4.4, :pipeline:`$out` can output to a collection in
391
- a different database. In earlier versions, :pipeline:`$out` can output
392
- to a collection to the same database where the aggregation is run.
390
+ Starting in MongoDB 4.4:
391
+
392
+ - :pipeline:`$out` can output to a collection in
393
+ a different database. In earlier versions, :pipeline:`$out` can only
394
+ output to a collection in the same database database where the
395
+ aggregation is run.
396
+
397
+ - :pipeline:`$out` can only run on replica set secondary nodes if
398
+ all the nodes in cluster have
399
+ :ref:`featureCompatibilityVersion <view-fcv>` set to ``4.4`` or
400
+ higher and the :doc:`/core/read-preference` allows secondary reads.
401
+ Check your :driver:`driver </>` documentation to see when your
402
+ driver added support.
393
403
394
404
``$indexStats``
395
405
```````````````
@@ -417,6 +427,20 @@ Starting in MongoDB 4.4 (also available starting in 4.2.4),
417
427
``$merge``
418
428
``````````
419
429
430
+ Starting in MongoDB 4.4:
431
+
432
+ - :pipeline:`$merge` can output to a collection in
433
+ a different database. In earlier versions, :pipeline:`$merge` can
434
+ only output to a collection in the same database where the aggregation
435
+ is run.
436
+
437
+ - :pipeline:`$merge` can only run on replica set secondary nodes if
438
+ all the nodes in cluster have
439
+ :ref:`featureCompatibilityVersion <view-fcv>` set to ``4.4`` or
440
+ higher and the :doc:`/core/read-preference` allows secondary reads.
441
+ Check your :driver:`driver </>` documentation to see
442
+ when your driver added support.
443
+
420
444
.. include:: /includes/fact-merge-same-collection-behavior.rst
421
445
422
446
.. include:: /includes/fact-merge-same-collection-warning.rst
0 commit comments