[SERVER-81334] Understand and document the behavior of a stream processor when an input collection is recreated mid-stream. Created: 22/Sep/23  Updated: 29/Oct/23  Resolved: 02/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Sandeep Dhoot Assignee: Matthew Normyle
Resolution: Fixed Votes: 0
Labels: init-337-m3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Atlas Streams
Backwards Compatibility: Fully Compatible
Participants:

 Comments   
Comment by Matthew Normyle [ 02/Oct/23 ]

From discussion with PMs, the preferred behavior is (1) below. SERVER-79438 will finish implementing this.

 
suppose I have a changestream $source and the collection gets dropped and re-created. What behavior do you prefer: # The streamProcessor keeps going, the user will see drop and invalidate events in their stream, and then continue to see usual insert etc events.

  1. The streamProcessor fails out.

 

https://mongodb.slack.com/archives/C04AH2TF7E1/p1696009449080679

Generated at Thu Feb 08 06:46:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.