-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We currently don't have good coverage for the un-happy path of shardCollection in core_sharding. In particular, we don't have good coverage for all those cases in which we expect shardCollection to fail for an incompatible state of the pre-existing collection.
For instance, when the existing collection has a unique index and the requested shard key is not a prefix of this index key we expect shardCollection to fail with InvalidOptions.
- related to
-
SERVER-100844 Sharding an unsharded collection fails if a stale unique index remains on the DB-primary shard
-
- Closed
-