[SERVER-51113] Write the test case for splitVector in database_versioning_all_commands.js Created: 23/Sep/20 Updated: 16/May/23 Resolved: 16/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Allison Easton |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Sprint: | Sharding EMEA 2023-05-29 |
| Participants: |
| Description |
|
mongos does forward splitVector to the primary shard so we should add a test case for that here. |
| Comments |
| Comment by Allison Easton [ 16/May/23 ] |
|
Although split vector does get sent to the database primary, it doesn't participate in the database versioning protocol. So it doesn't really make sense to add a test case here since the test is doing movePrimaries and checking that the database versioning protocol correctly re-targets the command, which it won't in the case of splitVector. |