[SERVER-30381] Remove handing for rolling back dropSource collections Created: 27/Jul/17  Updated: 30/Oct/23  Resolved: 06/Sep/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: Backlog
Fix Version/s: 3.5.13

Type: Task Priority: Major - P3
Reporter: Allison Chang Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-30371 Separate renameCollection across DB c... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-09-11
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 06/Sep/17 ]

Author:

{'username': 'benety', 'name': 'Benety Goh', 'email': 'benety@mongodb.com'}

Message: SERVER-30381 Remove handing for rolling back dropSource collections
Branch: master
https://github.com/mongodb/mongo/commit/456ba544978a0d41a2261bf65da686874fb631a2

Generated at Thu Feb 08 04:23:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.