-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Storage Execution
-
Execution Team 2022-11-14, Execution Team 2022-11-28
We anticipate using the BatchedWriteContext class to replicate groups of inserts for internal operations, such as renameCollection. Currently, batched operations are unconditionally replicated as applyOps oplog entries. For singleton batched operations, it would be ideal to replicate as the underlying CRUD operation type, in this case as a single āiā insert CRUD operation.
Since there is no user-facing command that would generate a batch of inserts, this would be a good opportunity to introduce a C++ unit test to exercise some of the BatchedWriteContext functionality for handling single and multiple inserts.
- has to be done after
-
SERVER-70897 move BatchedWriteContext into db/transaction or db/op_observer/
- Closed
- is related to
-
SERVER-70544 Multideletes with a single document should not be applyOps entries
- Closed