DOCS-1463 update renameCollection documents for sharded collections, resource locking, and exceptions

Author: ajhuh-mdb

source/includes/extracts-mongos-operations.yaml

@@ -21,12 +21,6 @@ content: |
    :dbcommand:`renameCollection` command and its helper
    :method:`db.collection.renameCollection()` to
    :writeconcern:`"majority"`.
-
-   .. note::
-
-      You cannot rename a sharded collection. You can however rename an
-      unsharded collection in a sharded cluster.
-
 ---
 ref: mongos-operations-wc-create
 content: |

source/reference/command/renameCollection.txt

@@ -97,7 +97,16 @@ Behavior
 Sharded Collections
 ~~~~~~~~~~~~~~~~~~~
 
-:dbcommand:`renameCollection` is **not** compatible with sharded collections.
+Starting in MongoDB 5.0, you can use the :dbcommand:`renameCollection` 
+command to change the name of a sharded collection. The target 
+database must be the same as the source database.
+
+Unsharded Collections
+~~~~~~~~~~~~~~~~~~~~~
+
+You can use :dbcommand:`renameCollection` to rename an unsharded 
+collection in a sharded cluster as long as the source and target 
+databases are on the same primary shard. 
 
 Existing Target Collection
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -122,14 +131,14 @@ If the target database differs from the source database,
 collection to the target collection. Depending on the size of the
 collection, this may take longer to complete.
 
-Resource Locking
-~~~~~~~~~~~~~~~~
+Resource Locking in Replica Sets
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. versionchanged:: 4.2
 
 If renaming a collection within the same database, 
-:dbcommand:`renameCollection` obtains an exclusive lock on the
-source and target collections for the duration of the operation. 
+:dbcommand:`renameCollection` obtains an exclusive lock on 
+the source and target collections for the duration of the operation. 
 All subsequent operations on the collections must wait until
 :dbcommand:`renameCollection` completes. 
 
@@ -208,17 +217,3 @@ equivalent to the previous example:
 
    use test
    db.orders.renameCollection( "orders2014" )
-
-Exceptions
-----------
-
-exception 10026
-   Raised if the ``source`` namespace does not exist.
-
-exception 10027
-   Raised if the ``target`` namespace exists and ``dropTarget`` is
-   either ``false`` or unspecified.
-
-exception 15967
-   Raised if the ``target`` namespace is an invalid collection
-   name.

source/release-notes/5.0.txt

@@ -297,6 +297,12 @@ for the ``"matchPrimaryNode"`` option. When set for a
 :binary:`~bin.mongod`, the instance follows the behavior specified for
 the ``"disabled"`` option.
 
+``renameCollection`` Compatible with Sharded Collections
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Starting in MongoDB 5.0, you can use the :dbcommand:`renameCollection` 
+command to change the name of a sharded collection.
+
 .. _5.0-rel-notes-shell:
 
 Shell Changes