[DOCS-16476] Incorrect resharding limitation about not allowing resharding on collections with a uniqueness constraint Created: 03/Nov/23  Updated: 06/Dec/23  Resolved: 16/Nov/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231120

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Nick Villahermosa
Resolution: Fixed Votes: 0
Labels: bugfix, quick-win, request
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
URL(s): https://www.mongodb.com/docs/manual/core/sharding-reshard-a-collection/
Participants:
Days since reply: 11 weeks, 6 days ago

 Description   

Our resharding docs say:

Resharding a collection that has a uniqueness constraint is not supported

This isn't quite true. Resharding requires that all existing unique indexes can be supported by the new shard key, using the same rules as shardCollection. So a collection with a uniqueness constraint can be resharded as long as that existing constraint is still satisfied per the rules here.



 Comments   
Comment by Nick Villahermosa [ 16/Nov/23 ]

Backports: 7.0, 6.0, 5.0

Comment by Alison Huh [ 06/Nov/23 ]

Thanks for flagging this issue, jack.mulrow@mongodb.com. We're expecting to pickup and complete this work soon!

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