[SERVER-78232] Change Stream is not working with on-demand materialized views Created: 20/Jun/23 Updated: 20/Jun/23 Resolved: 20/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.0.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kos Chaus | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: |
Expected: The change in MV1 is caught by the watcher Actual: The change in MV1 is NOT caught by the watcher |
||||||||
| Participants: | |||||||||
| Description |
|
The same code works with a regular Mongo collection but doesn't catch any events happening to the on-demand materialized view.
I found the test which checks that the Change Stream is not supported for normal views. However, I didn't find any limitations/restrictions to using Change Streams with on-demand materialized views.
|