[SERVER-35029] Add change stream notification for database drop Created: 16/May/18  Updated: 29/Oct/23  Resolved: 19/Jun/18

Status: Closed
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: 4.0.1, 4.1.1

Type: Task Priority: Major - P3
Reporter: Nicholas Zolnierz Assignee: Nicholas Zolnierz
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by DRIVERS-504 Update ChangeStream tests for 4.1.1 "... Closed
Documented
is documented by DOCS-11829 Docs for SERVER-35029: Add change str... Closed
Related
is related to JAVA-2939 ChangeStream can't handle 'drop' event Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0
Sprint: Query 2018-06-18, Query 2018-07-02
Participants:

 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.


 Comments   
Comment by Githook User [ 02/Jul/18 ]

Author:

{'username': 'nzolnierzmdb', 'name': 'Nick Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com'}

Message: SERVER-35029: Add change stream notification for database drop

(cherry picked from commit 77f43172584a0302df127174b9b0bd2259730772)
Branch: v4.0
https://github.com/mongodb/mongo/commit/e55a7996a7338c6ef3571050cab0aad641a7bf07

Comment by Githook User [ 19/Jun/18 ]

Author:

{'username': 'nzolnierzmdb', 'name': 'Nick Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com'}

Message: SERVER-35029: Add change stream notification for database drop
Branch: master
https://github.com/mongodb/mongo/commit/77f43172584a0302df127174b9b0bd2259730772

Generated at Thu Feb 08 04:38:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.