[SERVER-8031] Allow dropping the _id index when you have a hashed _id index Created: 26/Dec/12 Updated: 06/Dec/22 Resolved: 22/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Matulef | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 3 |
| Labels: | gm-ack | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Query
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
If hashed indexes can function as unique indexes, then it's not really necessary to maintain both an index on {_id : 1} and one on {_id : "hashed"}. There's an obvious cost to maintaining both indexes (unless you need the original one for range queries). Thus if/when SERVER-5878 is implemented, the user should be allowed to drop the default {_id : 1} index. |
| Comments |
| Comment by Asya Kamsky [ 22/Jan/19 ] |
|
We don't expect that this will ever be a thing we will want to allow. |
| Comment by Gregory McKeon (Inactive) [ 19/Apr/18 ] |
|
moving to query team because linked issue is on query. |