Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 6.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Execution Team 2022-11-14, Execution Team 2022-12-12, Execution Team 2022-11-28, Execution Team 2022-12-26

This function was introduced to format unprepared multi-document transactions in the OpObserverImpl implementation. It has since been extended to handle prepared transactions and batched writes. As a prerequisite to extending batched writes to span multipl applyOps oplog entries, we should extract this function and add it to the TransactionsOperations for improved testability.

This refactor will also affect packTransactionStatementsForApplyOps.

is related to

SERVER-70572 support applyOps oplog entry chaining for BatchedWriteContext

Closed

related to

SERVER-71210 move packTransactionStatementsForApplyOps() from OpObserverImpl to TransactionOperations

Closed

SERVER-71671 move definition of hangAfterLoggingApplyOpsForTransaction fail point to TransactionOperations implementation

Closed

SERVER-71054 TransactionParticipant last write optime should be null at the beginning of logOplogEntries

Closed

SERVER-71069 add ReplOperation method for exporting pre/post image information for writing to the image collection

Closed

SERVER-71655 relax multi-timestamp constraint for muti-doc transactions outside logOplogEntries

Closed

SERVER-71657 improve const-ness of OpObserver transaction-related events for TransactionOperations parameter

Closed

SERVER-71842 simplify logApplyOps (op_observer_impl.cpp) return type

Closed

(3 related to)

Assignee:: Benety Goh

Reporter:: Benety Goh

Participants:: Benety Goh, Githook User

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: Oct 27 2022 03:54:41 PM UTC

Updated:: Oct 29 2023 09:31:23 PM UTC

Resolved:: Dec 15 2022 08:52:29 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates