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

Add destined recipient to oplog entries from updates

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • Sharding 2020-09-21, Sharding 2020-10-05, Sharding 2020-10-19

    Description

      • Add CollectionUpdateArgs::destinedRecipient member to store the destined recipient.
      • Set CollectionUpdateArgs::destinedRecipient to the result of getDestinedRecipient() in update_stage.cpp.
        • It is acceptable for the work on this ticket to use either oldObj or newObj when calling getDestinedRecipient(). There will be separate work to handle the case when an update is modifying the document's shard key value under the new shard key pattern.
      • Call MutableOplogEntry::setDestinedRecipient() with the CollectionUpdateArgs::destinedRecipient member in MutableOplogEntry::makeUpdateOperation(). (for transactions)
      • Call MutableOplogEntry::setDestinedRecipient() with the CollectionUpdateArgs::destinedRecipient member in replLogUpdate(). (for non-transactions)

      Attachments

        Issue Links

          Activity

            People

              alex.taskov@mongodb.com Alexander Taskov (Inactive)
              max.hirschhorn@mongodb.com Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: