Description

The renameCollection documentation is not mentioning a current limitation in sharded clusters: it is not supported the rename of an unsharded collection if source and target database primary shards are different.

There is also a test showing that this scenario is expected to fail.

The following sentence should be reformulated.

FROM:
"You cannot rename a sharded collection. You can however rename an unsharded collection in a sharded cluster."

TO something like:

"You cannot rename a sharded collection. You can however rename an unsharded collection in a sharded cluster as long as source and target databases are residing on the same primary shard."

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)