[SERVER-36510] Rename Collection does not save/restore cursor between commits Created: 07/Aug/18  Updated: 29/Oct/23  Resolved: 17/Aug/18

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

Type: Bug Priority: Major - P3
Reporter: Ben Judd Assignee: Ben Judd
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-55394 Renaming a collection across database... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2018-08-13, Storage NYC 2018-08-27
Participants:

 Description   

WriteUnitOfWork Commit invalidates all cursors semantically; WT allows them to be read still if the item they were "over" did not get deleted; however, in other StorageEngines this may not hold.



 Comments   
Comment by Louis Williams [ 22/Mar/21 ]

As a side effect, this ticket allowed renames between databases to batch writes instead of copying documents one-by-one.

Comment by Githook User [ 17/Aug/18 ]

Author:

{'name': 'Ben Judd', 'email': 'ben.judd@10gen.com', 'username': 'Icantjuddle'}

Message: SERVER-36510 Rename now respects Cursor invalidation on WriteUnitOfWork Commit
Branch: master
https://github.com/mongodb/mongo/commit/3b1f4c92c4f48084af7002e597c8e8e14ba103f5

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