Probably worth making a quick note of this restriction
Engineering Ticket Description:
We currently allow renameCollection from the "local" database to a replicated database. This doesn't make a lot of sense; the local collections may be different on each replica, so doing so will result in an inconsistent set.
We also allow renameCollection from a replicated DB to an unreplicated one; this usually works but will cause problems if the local collection exists and dropExisting isn't specified.
Scope of changes
- Will add to renameCollection command behavior (but without version) (shell method cannot rename to a different database - so no change there)
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
SERVER-29825 Do not allow rename from unreplicated to replicated DB or vice-versa