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

Preventing dropping the last shard key index doesn't consider collection uniqueness

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • CAR Team 2024-02-05, CAR Team 2024-02-19

      shardCollection takes a unique parameter that when true requires there is an index supporting that shard key that also guarantees uniqueness for the shard key field. After SERVER-6491, we don't allow dropping the last index supporting the shard key, but we don't consider if the collection was sharded with unique:true. This lets a unique:true sharded collection be supported by a non-unique index if the unique index supporting it is dropped but there is another non-unique index supporting the shard key fields.

            Assignee:
            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: