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

updateZoneKeyRange command doesn't restrict hashed field values to NumberLong, if zone ranges are updated after sharding the collection

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: None
    • Minor Change
    • v4.4
    • Sharding 2020-05-04

      If zones ranges are created on a hashed shard key before sharding the collection, shardCollection command will fail if the zones range are not of type NumberLong. But updateZoneKeyRange command doesn't fail if zone ranges are updated after sharding the collection and the hashed field values are not NumberLong.

      This is bit inconsistent and error prone since users could potentially create zones ranges which cannot receive any data.

      This line in the test should fail when the shard key is hashed.

            Assignee:
            gregory.noma@mongodb.com Gregory Noma
            Reporter:
            arun.banala@mongodb.com Arun Banala
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: