-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Execution Team 2021-11-29
The OpObserver::aboutToDelete() callback was added in SERVER-21382 to support sharding migration enhancements. It currently accepts a collection NamespaceString and a snapshot of the document that will be removed. It would be useful for OpObserver::aboutToDelete() implementations to have access to the UUID and make this function more consistent with the other CRUD-related callbacks (onInserts(), onUpdate(), and onDelete()).
- is related to
-
SERVER-60748 The `EachOnDeleteRequiresAboutToDelete` test case invariants in `aboutToDelete` and not in `onDelete`
- Closed
-
SERVER-31540 Change uses of boost::optional of UUID to UUID in the sharding codebase
- Closed
-
SERVER-21382 Sharding migration transfers all document deletions
- Closed
-
SERVER-27987 Store collection UUIDs in the database catalogs
- Closed
-
SERVER-29294 make `db.createView()` command return the number of documents in the view
- Closed