[SERVER-67509] provide additional OpObserver hooks for multi-document transaction life-cycle events Created: 24/Jun/22 Updated: 29/Oct/23 Resolved: 19/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Matt Kneiser |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution Team 2022-10-17, Execution Team 2022-12-26, Execution Team 2023-01-23 | ||||||||
| Participants: | |||||||||
| Description |
|
The OpObserver interface currently supports events for aborting and committing multi-document transactions, but not when the multi-document transaction starts. For completeness and better extensibility, it would be nice to also be able to track when we create or begin a multi-document transaction (e.g. in the service entry point at the command invocation layer). |
| Comments |
| Comment by Githook User [ 18/Jan/23 ] |
|
Author: {'name': 'Matt Kneiser', 'email': 'matt.kneiser@mongodb.com', 'username': 'themattman'}Message: |