[SERVER-30224] Need completion flag field in db.coll.getIndexes() output. Created: 19/Jul/17 Updated: 27/Oct/23 Resolved: 30/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | 아나 하리 | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Query
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
When creating index as background, So this may lead to user misunderstanding that index creation is done. But users who doesn't know in detail, they might think index creation is done even during under creation. When user want to replace new index, some users may execute drop old index as soon as possible after building new index. But on secondary drop index command will executed before creating new index. This is nightmare to operators.
So, I think it would be better that mongod server will show whether it is completed or building status on db.getIndexes() command. For example ..
Thanks. |
| Comments |
| Comment by Eric Milkie [ 30/Nov/17 ] |
|
As of |
| Comment by Eric Milkie [ 19/Nov/17 ] |
|
We are in fact already making that behavior change in |
| Comment by Asya Kamsky [ 21/Jul/17 ] |
|
Would it be more correct for db.collection.getIndexes() not to show the index that is in process of being built (so it would only show up once it's built) |
| Comment by Kelsey Schubert [ 19/Jul/17 ] |
|
Hi matt.lee, Thank you for the feature request. I've sent it to the Query Team for consideration. Please continue tot watch for updates. Kind regards, |