[SERVER-34290] rollback via refetch assumes dropTarget field is always present Created: 03/Apr/18  Updated: 29/Oct/23  Resolved: 05/Apr/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.7.4

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2018-04-09
Participants:
Linked BF Score: 89

 Description   

Before SERVER-34196, renameCollection oplog entries always contained a dropTarget field that would be set to either a boolean value or a collection UUID. Now the server will omit the dropTarget field if it doesn't drop any collections during the rename; if the dropTarget field is present, it must be a UUID.

This does not apply to versions 3.6 and before.



 Comments   
Comment by Githook User [ 05/Apr/18 ]

Author:

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

Message: SERVER-34290 rollback via refetch handles missing dropTarget field
Branch: master
https://github.com/mongodb/mongo/commit/8e5794077bd5bbaa0e43d39082659493567a3f62

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