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.
- depends on
-
SERVER-38397 make WiredTigerRecoveryUnit::State a general concept in RecoveryUnit
- Closed