[SERVER-4310] Inverse oplog (undo log) Created: 17/Nov/11 Updated: 06/Dec/22 Resolved: 08/Dec/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
Some users have asked whether the we could record the inverse of what's in the oplog, in order to perform roll-backward operations (e.g., record the values that get overwritten on updates). Obviously, this sort of thing gets hard/impractical in the presence of collection/database dropping, but even if the undos only went back to an empty collection/db, it could be useful for some problems. |
| Comments |
| Comment by Eric Milkie [ 08/Dec/16 ] |
|
We decided not to do this. |