[SERVER-74516] Implement DocumentSourceChangeStreamCheckMulticastEvent Created: 01/Mar/23 Updated: 03/Apr/23 Resolved: 03/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mickey Winters | Assignee: | Backlog - Query Execution |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Participants: | |||||||||
| Story Points: | 12 | ||||||||
| Description |
|
after the underlying DocumentSourceCursor fetches a new batch, this stage should retrive the latest events from the multicast change collection. it will then merge child documents with the events from the multicast collection and throw TennantMigrationCommitted if it hits a split or merge no-op. |
| Comments |
| Comment by Mickey Winters [ 01/Mar/23 ] |
|
if the multicast change collection isn't ready we can just used an unmanaged collection to unit test |