Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13519

Investigate changes in SERVER-46505: Add back requirement that full shard key must be in query to update a shard key value

      Description

      Downstream Change Summary

      This fixed a targeting bug that was introduced by SERVER-42390. Marking as docs needed because this was discovered as part of the docs review for SERVER-42390.

      Description of Linked Ticket

      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.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

            Assignee:
            kay.kim@mongodb.com Kay Kim (Inactive)
            Reporter:
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              4 years, 3 weeks, 3 days ago