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

Verify the uniqueness property of a shard key cannot be changed by a shard key refine

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • Sharding 2019-07-29, Sharding 2019-08-12

      When a collection is sharded, a user can provide the "unique" option, which if true will ensure there exists an index with a uniqueness constraint with the same pattern as the proposed shard key. A user is not able to modify this property when refining a shard key, and this should be verified by inspecting the config.collections entry for both a unique=true and unique=false sharded collection after refining its shard key.

            Assignee:
            jamie.heppenstall@mongodb.com James Heppenstall (Inactive)
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: