[SERVER-15693] DBClientWithCommands should not cache ensureIndex calls Created: 16/Oct/14 Updated: 02/Apr/18 Resolved: 02/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | Andy Schwerin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
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 |
| Comments |
| Comment by Andy Schwerin [ 02/Apr/18 ] |
|
This code has long since disappeared on the master branch. |