[SERVER-82794] Preventing dropping the last shard key index doesn't consider collection uniqueness Created: 03/Nov/23  Updated: 06/Feb/24

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Pol Pinol
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Catalog and Routing
Operating System: ALL
Sprint: CAR Team 2024-02-05, CAR Team 2024-02-19
Participants:
Story Points: 2

 Description   

shardCollection takes a unique parameter that when true requires there is an index supporting that shard key that also guarantees uniqueness for the shard key field. After SERVER-6491, we don't allow dropping the last index supporting the shard key, but we don't consider if the collection was sharded with unique:true. This lets a unique:true sharded collection be supported by a non-unique index if the unique index supporting it is dropped but there is another non-unique index supporting the shard key fields.


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