Docsp 15767 forwardport (#3142)

* Removed self-links and 4.2 behavior

* Added release note for compact support with time series collections

Author: nvillahermosa-mdb

source/reference/command/compact.txt

@@ -18,8 +18,8 @@ Definition
 .. dbcommand:: compact
 
    Rewrites and defragments all data and indexes in a collection. On
-   :ref:`WiredTiger <storage-wiredtiger>` databases, this command will release
-   unneeded disk space to the operating system.
+   :ref:`WiredTiger <storage-wiredtiger>` databases, this command
+   releases unneeded disk space to the operating system.
 
 Syntax
 ------
@@ -39,13 +39,6 @@ Command Fields
 
 The command takes the following fields:
 
-.. note:: Starting in MongoDB 4.2
-
-
-   MongoDB removes the MMAPv1 storage engine and the MMAPv1 specific
-   options ``paddingFactor``, ``paddingBytes``, ``preservePadding``
-   for :dbcommand:`compact`.
-
 
 .. list-table::
    :header-rows: 1
@@ -65,16 +58,9 @@ The command takes the following fields:
 
        .. _compact-force-option:
 
-       Optional. Starting in v4.4, if specified, forces 
-       :dbcommand:`compact` to run on the :term:`primary` in 
-       a :term:`replica set`. Before v4.4, this boolean field 
-       enabled :dbcommand:`compact` to run on the :term:`primary` 
-       in a :term:`replica set` if the value was ``true`` and 
-       returned an error when run on a :term:`primary` if the 
-       value was ``false``, because the command blocked all other 
-       operations.
-      
-       Starting in v4.4, :dbcommand:`compact` does not block 
+       Optional. If specified, forces 
+       ``compact`` to run on the :term:`primary` in 
+       a :term:`replica set`. ``compact`` does not block 
        :ref:`crud` on the database it is compacting. 
 
    * - ``comment``
@@ -84,7 +70,7 @@ The command takes the following fields:
 
 
 .. warning:: Always have an up-to-date backup before performing server
-   maintenance such as the :dbcommand:`compact` operation.
+   maintenance such as the ``compact`` operation.
 
 .. _compact-authentication:
 
@@ -94,7 +80,7 @@ The command takes the following fields:
 For clusters enforcing :ref:`authentication <authentication>`,
 you must authenticate as a user with the :authaction:`compact` privilege
 action on the target collection. The :authrole:`dbAdmin` role provides 
-the required privileges for running :dbcommand:`compact` against
+the required privileges for running ``compact`` against
 non-system collections. 
 
 For more information on configuring the ``resource`` document, see 
@@ -140,9 +126,6 @@ Blocking behavior is version specific.
    * - Version
      - Blocking Behavior
 
-   * - Pre 4.4
-     - ``compact`` blocks all read and write activity.
-
    * - 4.4
      - - .. include:: /includes/reference/compact-methods-list.rst
        - All other operations are permitted.
@@ -167,14 +150,14 @@ Operation Termination
 
 If you terminate the operation with the :method:`db.killOp()
 <db.killOp()>` method or restart the server before the
-:dbcommand:`compact` operation has finished, be aware of the following:
+``compact`` operation has finished, be aware of the following:
 
 - If you have journaling enabled, the data remains valid and
-  usable, regardless of the state of the :dbcommand:`compact` operation.
+  usable, regardless of the state of the ``compact`` operation.
   You may have to manually rebuild the indexes.
 
 - If you do not have journaling enabled and the :binary:`~bin.mongod` or
-  :dbcommand:`compact` terminates during the operation, it is impossible
+  ``compact`` terminates during the operation, it is impossible
   to guarantee that the data is in a valid state.
 
 - In either case, much of the existing free space in the collection may
@@ -187,14 +170,14 @@ Disk Space
 To see how the storage space changes for the collection, run the
 :dbcommand:`collStats` command before and after compaction.
 
-On :ref:`WiredTiger <storage-wiredtiger>`, :dbcommand:`compact` attempts
+On :ref:`WiredTiger <storage-wiredtiger>`, ``compact`` attempts
 to reduce the required storage space for data and indexes in a
 collection, releasing unneeded disk space to the operating system. The
 effectiveness of this operation is workload dependent and no disk space
 may be recovered. This command is useful if you have removed a large
 amount of data from the collection, and do not plan to replace it.
 
-:dbcommand:`compact` may require additional disk space to run on
+``compact`` may require additional disk space to run on
 WiredTiger databases.
 
 .. _compact-cmd-replica-sets:
@@ -250,11 +233,6 @@ Blocking behavior on secondary nodes is version specific.
    * - Version
      - Blocking Behavior
 
-   * - Pre 4.4
-     - - ``compact`` blocks all read and write activity.
-       - No replication possible.
-       - Secondary node is in :replstate:`RECOVERING` state.
-
    * - 4.4
      - - ``compact`` blocks all write activity.
        - No replication possible.
@@ -277,20 +255,20 @@ For replica set maintenance and availability, see
 Sharded Clusters
 ~~~~~~~~~~~~~~~~
 
-:dbcommand:`compact` only applies to :binary:`~bin.mongod` instances. In a
-sharded environment, run :dbcommand:`compact` on each shard separately
+``compact`` only applies to :binary:`~bin.mongod` instances. In a
+sharded environment, run ``compact`` on each shard separately
 as a maintenance operation.
 
-You cannot issue :dbcommand:`compact` against a :binary:`~bin.mongos` instance.
+You cannot issue ``compact`` against a :binary:`~bin.mongos` instance.
 
 Capped Collections
 ~~~~~~~~~~~~~~~~~~
 
-On :ref:`WiredTiger <storage-wiredtiger>`, the :dbcommand:`compact`
+On :ref:`WiredTiger <storage-wiredtiger>`, the ``compact``
 command will attempt to compact the collection.
 
 Index Building
 ~~~~~~~~~~~~~~
 
 :binary:`~bin.mongod` rebuilds all indexes in parallel following the
-:dbcommand:`compact` operation.
+``compact`` operation.

source/release-notes/6.3.txt

@@ -137,8 +137,8 @@ Starting in MongoDB 6.3, these server parameters were added:
 - :parameter:`chunkMigrationConcurrency` sets the number of threads on
   the source shard and the receiving shard for migrating chunks.
 
-Time Series Collection Parameters
----------------------------------
+Time Series Collection Custom Bucketing Parameters
+--------------------------------------------------
 
 MongoDB 6.3 adds the following :ref:`time series parameters 
 <time-series-fields>`:
@@ -148,6 +148,12 @@ MongoDB 6.3 adds the following :ref:`time series parameters
 - ``bucketRoundingSeconds`` sets the time interval that determines the 
   starting timestamp for a new bucket.
 
+``compact`` Support for Time Series Collections
+-----------------------------------------------
+
+Starting in MongoDB 6.3, the :dbcommand:`compact` command works with
+:ref:`time series collections <manual-timeseries-landing>`.
+
 Report an Issue
 ---------------