[SERVER-30382] Create new oplog entry for handling cross database renameCollections Created: 27/Jul/17 Updated: 27/Oct/23 Resolved: 06/Sep/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Chang | Assignee: | Backlog - Replication Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
Make a new oplog entry for handling cross database renameCollections that combines renaming a temp collection to a permanent collection and dropping the source collection. This will ensure that during rollback, both of these operations are rolled back, preventing a situation where only the drop source is rolled back, leaving both collections present. |
| Comments |
| Comment by Benety Goh [ 06/Sep/17 ] |
|
|