[SERVER-55394] Renaming a collection across databases no longer batches writes Created: 22/Mar/21  Updated: 29/Oct/23  Resolved: 26/Apr/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.9.0
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-36510 Rename Collection does not save/resto... Closed
is related to SERVER-48771 Enforce constraints on "multi-timesta... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2021-05-03
Participants:

 Description   

Due to changes in SERVER-48771, renaming a collection across databases no longer batches writes, and instead copies documents one-by-one. This is a regression from SERVER-36510, which did not explicitly state this as a change in the ticket, but allowed rename to batch writes.



 Comments   
Comment by Githook User [ 23/Apr/21 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-55394 batch temporary collection inserts when renaming across databases
Branch: master
https://github.com/mongodb/mongo/commit/124ee49878b8fe8a43fda758408178be9db0ccf5

Comment by Githook User [ 23/Apr/21 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-55394 improve invariants in renameBetweenDBs()
Branch: master
https://github.com/mongodb/mongo/commit/5f83ead2140911d2ea35406ad1cfd7250dc6e00a

Generated at Thu Feb 08 05:36:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.