[SERVER-35401] Whole-db and whole-cluster change streams do not filter operations to "system" collections Created: 05/Jun/18 Updated: 29/Oct/23 Resolved: 12/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc6, 4.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Nicholas Zolnierz |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | read-only-views | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v4.0
|
||||
| Sprint: | Query 2018-06-18 | ||||
| Participants: | |||||
| Description |
|
Easily reproduced by creating a view on the database being watched. For whole-db change streams, there is no notification generated. For whole-cluster change streams, an "insert" is returned on the "system.views" collection. |
| Comments |
| Comment by Githook User [ 14/Jun/18 ] |
|
Author: {'username': 'nzolnierzmdb', 'name': 'Nick Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com'}Message: (cherry picked from commit 12f7795c52a7d352da1a7e03f71a233624dc05d4) |
| Comment by Githook User [ 12/Jun/18 ] |
|
Author: {'username': 'nzolnierzmdb', 'name': 'Nick Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com'}Message: |
| Comment by Nicholas Zolnierz [ 05/Jun/18 ] |
|
Per discussion with asya, the desired behavior is to filter out all changes to internal "system" collections, including CRUD and metadata operations. |