[SERVER-30665] applyOps collMod handling should only allow nonexistent UUIDs for UUID upgrade collMods Created: 15/Aug/17  Updated: 30/Oct/23  Resolved: 17/Aug/17

Status: Closed
Project: Core Server
Component/s: Replication, Storage
Affects Version/s: None
Fix Version/s: 3.5.12

Type: Bug Priority: Major - P3
Reporter: Maria van Keulen Assignee: Maria van Keulen
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: Storage 2017-08-21
Participants:
Linked BF Score: 0

 Description   

Currently, a collMod oplog entry with a nonexistent UUID will be applied to an existing collection if the collection name of the oplog entry matches an existing collection name. This is due to the handling of collMods that are used to upgrade from 3.4 to 3.6 and add UUIDs to collections. This special handling should only occur for collMods that are for upgrade, i.e., empty collMods.



 Comments   
Comment by Githook User [ 17/Aug/17 ]

Author:

{'username': 'mvankeulen94', 'email': 'maria@mongodb.com', 'name': 'Maria van Keulen'}

Message: SERVER-30665 Only accept nonexistent UUIDs for UUID upgrade collMods
Branch: master
https://github.com/mongodb/mongo/commit/c1aaff64cdf88d3ff2f0220033964fa6fcdb5513

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