-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: Backlog
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2017-09-11
After rename across databases is split into separate oplog entries for creating a new collection, inserting the documents and dropping the source collection, we no longer need to have the handling for rolling back collections dropped by the dropSource field in the renameCollection oplog.
Remove the function
FixUpInfo::recordCrossDatabaseRenameRollbackInfo
from rs_rollback.cpp/.h.
- depends on
-
SERVER-30371 Separate renameCollection across DB commands into individual oplog entries
- Closed