-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Labels:None
Description
updateZoneKeyRange now restricts zone range fields corresponding to hashed shard key fields to be NumberLong, MinKey, or MaxKey.
Description of Linked Ticket
If zones ranges are created on a hashed shard key before sharding the collection, shardCollection command will fail if the zones range are not of type NumberLong. But updateZoneKeyRange command doesn't fail if zone ranges are updated after sharding the collection and the hashed field values are not NumberLong.
This is bit inconsistent and error prone since users could potentially create zones ranges which cannot receive any data.
This line in the test should fail when the shard key is hashed.
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
- documents
-
SERVER-44865 updateZoneKeyRange command doesn't restrict hashed field values to NumberLong, if zone ranges are updated after sharding the collection
-
- Closed
-