[DOCS-13608] Investigate changes in SERVER-44865: updateZoneKeyRange command doesn't restrict hashed field values to NumberLong, if zone ranges are updated after sharding the collection Created: 21/Apr/20  Updated: 13/Nov/23  Resolved: 11/Aug/21

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.7.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Naomi Pentrel (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-44865 updateZoneKeyRange command doesn't re... Closed
Participants:
Days since reply: 2 years, 26 weeks ago
Epic Link: DOCSP-15042
Story Points: 2

 Description   

Description

Downstream Change Summary

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.)



 Comments   
Comment by Githook User [ 11/Aug/21 ]

Author:

{'name': 'Naomi Pentrel', 'email': '5212232+npentrel@users.noreply.github.com', 'username': 'npentrel'}

Message: DOCS-13608: updateZoneKeyRange with hashed shard key
Branch: master
https://github.com/mongodb/docs/commit/def82fcfcf61e69769362b13096fe4b318bdc33b

Generated at Thu Feb 08 08:08:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.