[SERVER-37492] [3.6] Change streams on a non-existent collection are invalidated by a database drop Created: 05/Oct/18 Updated: 27/Oct/23 Resolved: 12/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Operating System: | ALL |
| Participants: |
| Description |
|
As part of 4.0, we added change streams notifications for database drops and consciously decided that single-collection change streams should remain open if the collection never existed (some discussion in the review for This is different behavior in 3.6 as the single-collection change streams are invalidated if the database is dropped. We should decide on a consistent approach and document it. |
| Comments |
| Comment by Ian Whalen (Inactive) [ 12/Oct/18 ] |
|
nicholas.zolnierz to talk with docs team about documenting database drops invalidating all changestreams. no need to mention existence/non-existence. |
| Comment by Nicholas Zolnierz [ 05/Oct/18 ] |