[SERVER-79652] Refactor the initial split policy for data in primary shard Created: 03/Aug/23 Updated: 26/Oct/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | oldshardingemea | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Catalog and Routing
|
| Participants: |
| Description |
|
SERVER-79179 introduced a new initial split policy in order to specify the shard where the data will be stored, considering that, we could refactor things so we can express the new policy based in the other, we would need to pass a shard (or the primary shard) in the constructor, and we could remove the primary shard from the SplitPolicyParam type. |