[SERVER-34251] change_stream_whole_db_invalidation.js should check for invalidated change stream on system collection drop Created: 02/Apr/18 Updated: 29/Oct/23 Resolved: 02/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.4 |
| Type: | Bug | 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: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Query 2018-04-09 | ||||
| Participants: | |||||
| Linked BF Score: | 22 | ||||
| Description |
|
In particular, this drop will actually invalidate the change stream if the collection exists beforehand. The reason this is passing most of the time is because the collection drop doesn't write anything to the oplog when the collection doesn't exist. The test should assert that the collection exists before dropping, then asserting that the change stream is invalidated. |
| Comments |
| Comment by Githook User [ 02/Apr/18 ] |
|
Author: {'email': 'nicholas.zolnierz@mongodb.com', 'name': 'Nick Zolnierz', 'username': 'nzolnierzmdb'}Message: |