[SERVER-77366] add OpAccumulator to OpObserver::aboutToDelete() Created: 22/May/23  Updated: 29/Oct/23  Resolved: 23/May/23

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

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

Issue Links:
Related
is related to SERVER-76271 Remove OpObserverShardingImpl Depende... Closed
is related to SERVER-76369 Accumulate state among early OpObservers Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2023-05-29
Participants:

 Description   

This is a follow up to SERVER-76369 in which we introduced a mechanism for sharing limited state across invocations on the same CRUD method across different op observer implementations.



 Comments   
Comment by Githook User [ 23/May/23 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-77366 OpObserver::aboutToDelete accepts OpStateAccumulator
Branch: master
https://github.com/mongodb/mongo/commit/d5dff6d99d6b569864e7dd71a8bea88f9017aa3c

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