-
Type:
Improvement
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
DBClientWithCommands::ensureIndex() performs a no-op if ensureIndex has already been called on the same index earlier in the object's lifetime. This is confusing behavior (the no-op is incorrect if the index or collection was dropped through other means) and should be removed.
See also linked ticket SERVER-7168.
- related to
-
SERVER-7168 Don't cache ensureIndex in the shell
-
- Closed
-