[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: |
|
||||||||
| 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: |