[SERVER-55179] Reconsider how to handle duplicate documents in change streams update lookup Created: 12/Mar/21  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Aggregation Framework
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   

In an extremely limited set of circumstances, it is possible for a change stream updateLookup to return more than one document if there are multiple documents with the same _id on different shards of a recently-sharded collection. In such cases, we cannot determine which document the update refers to, and so we throw an exception to highlight this situation to the user. We should consider other ways of addressing this scenario.


Generated at Thu Feb 08 05:35:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.