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

XMLWordPrintableJSON

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

      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
            Reporter:
            Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: