When a collection is sharded, a user can provide the "unique" option, which if true will ensure there exists an index with a uniqueness constraint with the same pattern as the proposed shard key. A user is not able to modify this property when refining a shard key, and this should be verified by inspecting the config.collections entry for both a unique=true and unique=false sharded collection after refining its shard key.
Verify the uniqueness property of a shard key cannot be changed by a shard key refine
- Assignee:
-
James Heppenstall (Inactive)
- Reporter:
-
Jack Mulrow
- Votes:
-
0 Vote for this issue - Watchers:
-
2 Start watching this issue
- Created:
- Updated:
- Resolved: