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

Split OpObserver::onTransactionCommit() into two functions for unprepared and prepared transactions respectively

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.9
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • Sharding 2019-02-25

      As schwerin found, the onCommit OpObserver function for prepared transaction should be marked as noexcept, but the one for unprepared transaction is allowed to throw. Separating them makes the code clearer.

            Assignee:
            blake.oler@mongodb.com Blake Oler
            Reporter:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: