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:
- Avoid wasting time cloning before failing the commit
- Avoid repeatedly selecting invalid split points
This ticket is an optimization that will not be needed in case SERVER-12536 gets done.
- depends on
-
SERVER-12536 Only allow shard key types which can be used for an _id
-
- Closed
-
- related to
-
SERVER-73441 Make sure shard key bounds are valid when committing `moveRange`
-
- Closed
-
-
-
- Closed
-