[DOCS-14925] Investigate changes in SERVER-59399: Allow dropping an index during separate index build on the same collection Created: 11/Nov/21 Updated: 13/Nov/23 Due: 05/Feb/22 Resolved: 04/Feb/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Joseph Dougherty |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 2 years, 12 weeks, 6 days ago | ||||||||
| Epic Link: | DOCSP-17171 | ||||||||
| Story Points: | 2 | ||||||||
| Description |
|
Downstream Change Summary The dropIndexes command can now drop ready indexes while there are any in-progress index builds for the same collection. Description of Linked Ticket According to my understanding, it's currently not possible to drop an index on a collection at the same time that a separate index is in the process of being built on the same collection. As of I think this behavior is confusing (why should building index A interfere with dropping index B?) and makes it more difficult to manage indexes. |
| Comments |
| Comment by PM Bot [ 11/Nov/21 ] |
|
Downstream changes updated for upstream |