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

XMLWordPrintableJSON

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

      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:
            James Heppenstall (Inactive)
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: