[SERVER-34623] Add test for reading a change stream after movePrimary Created: 23/Apr/18 Updated: 06/Dec/22 Resolved: 04/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Participants: |
| Description |
|
The behavior is incorrect because of SERVER-34462. We should probably still have coverage for it though. |
| Comments |
| Comment by Asya Kamsky [ 25/Apr/18 ] |
|
I wonder if movePrimary oplog entries should have a flag similar to fromMigrate flag does for chunk migrations. Looks like SERVER-34462 describes that. |
| Comment by David Storch [ 23/Apr/18 ] |
|
ian.boros, I would suggest deprioritizing this work. This test will be much more valuable in the future if we make change streams work seamlessly with movePrimary. I'm reassigning this to the backlog user and moving into the Needs Triage queue. |