Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
None
Description
----------------------------
Original Description
Description:
No documentation summary in engineering ticket
Engineering Ticket Description:
From the scope doc:
- Change streams on a single collection will see a collection drop before the database drop, and will be invalidated by it. If a new stream is opened after the collection drop but before the database drop, it will be invalidated by the database drop.
- Change streams on the database being dropped will be invalidated.
- Change streams on the entire cluster will not be invalidated.
----------------------------
You can branch off master for this.
Scope of changes (files that need work and how much)
Impact to other docs outside of this product
MVP (work and date?)
Resources (e.g. Scope Docs, Invision)
Attachments
Issue Links
- documents
-
SERVER-35029 Add change stream notification for database drop
-
- Closed
-
- is duplicated by
-
DOCS-11903 Docs for SERVER-33844: Change Streams - provide details for metadata operations instead of (or in addition to) invalidation
-
- Closed
-
- is related to
-
DOCS-11806 Docs for SERVER-35028: Add change stream notifications for collection drop and rename
-
- Closed
-