[SERVER-34416] Ignore drops and renames in whole-db or whole-cluster change streams Created: 11/Apr/18 Updated: 06/Dec/22 Resolved: 11/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Participants: |
| Description |
|
In the original design/implementation, these events would invalidate the stream. We would like to eventually create notifications for these events, but until we agree on a format we should simply skip them, not invalidate the stream. |