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

Ensure UpdateNoIndexes is propagated correctly

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • v7.0
    • 105

      When calling updateDocument() here:
      https://github.com/10gen/mongo/blob/v7.0/src/mongo/db/exec/update_stage.cpp#L269-L281

      Note that we compute the diff from the OpLog event, but there are only 2 choices: either the diff from the the oplog, or all indexes have been changed. But there is a third option: No indexes have changed. We need to pass that value through and handle it correctly in updateRecord() to avoid updating more indexes than we should, and to avoid going through the anyIndexesMightBeAffected() checks if it isn't needed.

            Assignee:
            colin.stolley@mongodb.com Colin Stolley
            Reporter:
            colin.stolley@mongodb.com Colin Stolley
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: