[SERVER-69933] Allow change stream to survive movePrimary Created: 23/Sep/22  Updated: 13/Jan/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Bernard Gorman Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Execution
Participants:

 Description   

At present, the movePrimary command will cause a single-collection change stream to be invalidated, because the operation ends by dropping the collection on the original shard. Instead, the stream should be able to continue reading events from the collection after it has been moved to the new shard. This will require the drop event to be marked as fromMigrate:true.

Additionally, the UUID of the collection on the new shard will be different than on the original (see this comment and SERVER-32847). This should be changed so that the UUID remains consistent throughout.


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