[SERVER-73537] `autoSplitVector` must not return invalid split points Created: 02/Feb/23 Updated: 26/Oct/23 |
|
| Status: | Blocked |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | oldshardingemea | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Before committing a migration this check is ensuring that the bounds are valid shard keys. Given that moveRange is choosing a bound relying on the output of autoSplitVector, we should make sure that it never returns invalid split points. This will help to:
This ticket is an optimization that will not be needed in case SERVER-12536 gets done. |