-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Labels:None
Description
Just for the record, don't know if the corner case was taken into account previously.
If a user tries to rename a collection to itself, starting from now an IllegalOperation is thrown. Before, a misleading NamespaceNotFound exception was thrown.
Description of Linked Ticket
If the collection exists, the collection version must be returned in a best-effort fashion, without acquiring any lock.
If the collection exists but dropTarget=true, an `IllegalOptions` error must be returned.
If the collection doesn't exist, a `NamespaceNotFound` error is already thrown both in case of RS or sharded cluster.
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
- backported by
-
DOCS-14499 [BACKPORT] [v5.0] Uniform `fromNss == toNss` rename behavior between rs and sharded cluster
- Closed
- documents
-
SERVER-56296 Uniform `fromNss == toNss` rename behavior between rs and sharded cluster
- Closed