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

Add back requirement that full shard key must be in query to update a shard key value

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4
    • Sprint:
      Sharding 2020-03-23

      Description

      SERVER-39158 added the requirement that to update the value of a document's shard key, the update's query must include an equality match on the full shard key. SERVER-42390 changed the treatment of missing shard key fields when targeting based on a user document (e.g. a replacement document in an update) but incorrectly removed the restriction that the full shard key must be present in a query to update a shard key value. This requirement should be added back.

        Attachments

          Issue Links

          is documented by

          Task - A task that needs to be done. DOCS-13519 Investigate changes in SERVER-46505: Add back requirement that full shard key must be in query to update a shard key value

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-39158 Change updates to prefer target by the query

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-42390 Allow documents in a sharded collection to not contain all shard key fields

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              jack.mulrow Jack Mulrow
              Reporter:
              jack.mulrow Jack Mulrow
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: