-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 4.1.6
-
Component/s: Sharding
-
Sharding
-
ALL
-
Sharding 2019-01-28, Sharding 2019-02-11, Sharding 2019-02-25
-
(copied to CRM)
Currently, if shard returns multiple errors, createIndex simply selects the first error it saw and puts it on the top level error field. Instead, it should prioritize other errors over CannotImplicitlyCreateCollection.
- duplicates
-
SERVER-38367 Descriptive error message for the inability to create unique indexes on arbitrary fields in sharded collections
- Closed
- related to
-
SERVER-43490 Validate if we can perform TODO listed in SERVER-38686
- Closed