-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Execution Team 2022-12-12
The logOplogEntries() function (within the OpObserverImpl implementation) formats applyOps oplog entries for multi-doc transactions and batched writes. In order to write out a chain of applyOps oplog entries and to write to the images collection while creating the oplog entries, it has to relax the multi-timestamp constraint on the RecoveryUnit. It would be beneficial in terms of separating the applyOps formatting logic from storage engine related settings to be able to update the RecoveryUnit prior to calling logOplogEntries().
This supports the work in SERVER-70899 where the TransactionOperations would be sole focused on formatting the applyOps entries without any explicit interaction with the OperationContext or RecoveryUnit.
- is related to
-
SERVER-70899 move logOplogEntries() from OpObserverImpl to TransactionOperations
- Closed
-
SERVER-48771 Enforce constraints on "multi-timestamp" transactions
- Closed
-
SERVER-71488 include multi-doc prepare info in TransactionOperations::getApplyOpsInfo() result
- Closed