[SERVER-70897] move BatchedWriteContext into db/transaction or db/op_observer/ Created: 27/Oct/22  Updated: 29/Oct/23  Resolved: 10/Nov/22

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

Type: Task Priority: Major - P3
Reporter: Benety Goh Assignee: Shin Yee Tan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done before SERVER-70898 replicate batched operations comprisi... Open
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-11-14
Participants:

 Description   

This class works as an aggregator of replicated operations (much like multi-doc transactions) and is closely related to the formatting of oplog entries (a primary reponsibility of the OpObserver and OplogWriter interfaces).

Moving this class into either of the subdirectories related to multif-doc transactions or the OpObserver interface would clarify its purpose.



 Comments   
Comment by Githook User [ 10/Nov/22 ]

Author:

{'name': 'Shin Yee Tan', 'email': 'shinyee.tan@mongodb.com', 'username': 'shinyeet'}

Message: SERVER-70897 move BatchedWriteContext into db/op_observer
Branch: master
https://github.com/mongodb/mongo/commit/e4fca0011ef46497a60821da4429fdd982981109

Generated at Thu Feb 08 06:17:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.