[SERVER-31190] Extend change_stream_invalidation.js Created: 20/Sep/17  Updated: 30/Oct/23  Resolved: 29/Sep/17

Status: Closed
Project: Core Server
Component/s: Aggregation Framework, Replication
Affects Version/s: None
Fix Version/s: 3.6.0-rc0

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Tess Avitabile (Inactive)
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-10-02
Participants:

 Description   

change_stream_invalidation.js currently tests the following scenarios:

  • When a collection is dropped, we return an "invalidate" entry and close the cursor.
  • It is not possible to resume a change stream after a collection drop, even if the invalidation has not been received.

We should extend it to test the following scenarios:

  • When a collection is dropped, if there are additional insert/update/delete entries that have not yet been received, the user can read the insert/update/delete entries preceding the invalidate entry.
  • It is possible to open a new change stream cursor on a collection that does not exist. When the collection is created, we start seeing oplog entries for that collection.


 Comments   
Comment by Githook User [ 29/Sep/17 ]

Author:

{'email': 'tess.avitabile@mongodb.com', 'name': 'Tess Avitabile', 'username': 'tessavitabile'}

Message: SERVER-31190 Extend change_stream_invalidation.js
Branch: master
https://github.com/mongodb/mongo/commit/e977f79fb37f7c6608bcfa7df81932b302285a57

Generated at Thu Feb 08 04:26:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.