Make sure shard key bounds are valid when committing `moveRange`

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.3.0-rc0, 6.0.6
    • Affects Version/s: 6.1.1, 6.0.4, 6.2.0-rc6
    • Component/s: Sharding
    • None
    • Sharding EMEA
    • Fully Compatible
    • ALL
    • v6.2
    • Sharding EMEA 2023-02-06
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Before committing a chunk split, there is a check ensuring that the split point is a valid shard key.

      Since the auto-splitter has been eliminated and split points are now selected in the moveRange path, we must adapt the migration commit to also check that the new bounds are valid shard keys.

              Assignee:
              Pierlauro Sciarelli
              Reporter:
              Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: