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

Change updates to prefer target by the query

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.12
    • Component/s: Querying, Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Minor Change
    • Operating System:
      ALL
    • Sprint:
      Query 2019-04-08, Query 2019-04-22, Query 2019-05-06, Query 2019-05-20, Query 2019-06-03
    • Case:

      Description

      Currently, replacement style updates target using the update rather than the query. We should change this to target using the query instead.

      As of today, we do not allow users to change the shard key for a document. If shard 1 owns the chunk with range (shardKey : min, shardKey : 500) and shard 2 owns the chunk with range (shardKey : 500, shardKey : max) and a user sends 

      db.coll.update({shardKey : 100}, {shardKey : 800})

      the update will be sent to shard 2 and we return 

      {ok: 1.0, nMatched : 0)

      We should actually get an ImmutableField error.

      Once we allow a user to update the shard key for a document (PM-1163), the above update should cause the document to change shards. However, since the update would be sent to shard 2, shard 1 will never actually see this update and the update will not be applied.

        Attachments

          Issue Links

          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-40338 Add tests that replacement style and pipeline updates can update the shard key value

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

          Task - A task that needs to be done. MONGOID-4759 Change updates to prefer target by the query

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

          Task - A task that needs to be done. DRIVERS-660 Change updates to prefer target by the query

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-40903 Ensure full shard key in query to allow shard key updates

          • Major - P3 - Major loss of function.
          • Closed
          is documented by

          Task - A task that needs to be done. DOCS-12742 Docs for SERVER-39158: Change updates to prefer target by the query

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-41184 Add metrics to indicate the amount of sharded updates done with only _id in query

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

          Bug - A problem which impairs or prevents the functions of the product. 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

            Activity

              People

              Assignee:
              arun.banala Arun Banala
              Reporter:
              janna.golden Janna Golden
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: