Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.2.0
Affects Version/s: None
Component/s: None
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Execution Team 2021-11-29
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: Benety Goh
Reporter:: Benety Goh
Participants:: Benety Goh, Githook User
Votes:: 0 Vote for this issue
Watchers:: 0 Start watching this issue

Created:: Nov 18 2021 11:47:09 PM UTC
Updated:: Oct 29 2023 09:45:48 PM UTC
Resolved:: Nov 19 2021 11:55:57 AM UTC
Confidence Status Last Update:: 19/Nov/21 10:41 AM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates