Remove commit/rollback logic for Changes from Storage Engine-specific RecoveryUnits

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Minor - P4
    • 4.3.1
    • Affects Version/s: 3.1.4
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • Quint 9 09/18/15, Execution Team 2019-06-17, Execution Team 2019-07-01
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Now nested units of work are removed (SERVER-18168), there is no need for storage engine specific RecoveryUnit's to deal with the concept of registering changes for commit or rollback. So, individual Storage Engines should not need to implement this logic. One potential way to address this is to move the Changes logic into the RecoveryUnit interface directly.

              Assignee:
              Maria van Keulen
              Reporter:
              Geert Bosch
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: