[SERVER-37388] renameCollection to itself always fails Created: 28/Sep/18  Updated: 06/Dec/22  Resolved: 12/Oct/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Storage Execution
Operating System: ALL
Steps To Reproduce:

(function() {
    assert.commandWorked(db.c.insert({}));
 
    // Fails with NamespaceNotFound
    assert.commandWorked(db.c.renameCollection("c", true));
})(); 

Participants:
Linked BF Score: 115

 Description   

When you rename a collection to the same namespace with dropTarget:true, first the command drops the namespace. Then the command fails when it attempts to rename the collection because the collection does not exist.



 Comments   
Comment by Eric Milkie [ 12/Oct/18 ]

This is a benign problem that will probably go away after SERVER-37443 is complete.

Generated at Thu Feb 08 04:45:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.