[SERVER-52694] Rely on Collection copy-on-write instead of restoring changes in rollback handler when possible Created: 09/Nov/20  Updated: 29/Oct/23  Resolved: 18/Nov/20

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

Type: Task Priority: Major - P3
Reporter: Henrik Edin Assignee: Henrik Edin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-11-16, Execution Team 2020-11-30
Participants:

 Comments   
Comment by Githook User [ 18/Nov/20 ]

Author:

{'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}

Message: SERVER-52694 Rely on Collection copy-on-write instead of restoring Collection in rollback handler

CollectionIndexUsageTrackerDecoration is separated from CollectionQueryInfo as they no longer have the same semantics. CollectionIndexUsageTrackerDecoration is shared between Collection instances and CollectionQueryInfo is not.
Fix UnmanagedCommitManagedRollback mode so it works when write conflict exception is thrown by managing it for rollback
Branch: master
https://github.com/mongodb/mongo/commit/fef6cc564d517b895b4857c73a9a794bd9987194

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