Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-8031

Allow dropping the _id index when you have a hashed _id index

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Index Maintenance, Sharding
    • Query

      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.

            Assignee:
            backlog-server-query Backlog - Query Team (Inactive)
            Reporter:
            matulef Kevin Matulef
            Votes:
            3 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: