[SERVER-34341] parseCollModUUIDAndNss should uassert the input UUID (if provided) is in the catalog Created: 05/Apr/18  Updated: 29/Oct/23  Resolved: 24/May/18

Status: Closed
Project: Core Server
Component/s: Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: 4.0.0-rc1, 4.1.1

Type: Task Priority: Major - P3
Reporter: Maria van Keulen Assignee: Xiangyu Yao (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0
Sprint: Storage NYC 2018-06-04
Participants:

 Description   

For MongoDB 3.6 UUID upgrade, the parseCollModUUIDAndNss function allowed an input UUID to not exist in the UUID Catalog if the collMod was empty, since collMod was used to add UUIDs to collections. Instead, parseCollModUUIDAndNss should assert that the UUID (if provided) exists in the catalog because this function is only used during oplog application and there are no replicated UUID upgrade collMods in MongoDB 4.0.



 Comments   
Comment by Githook User [ 24/May/18 ]

Author:

{'username': 'xy24', 'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com'}

Message: SERVER-34341 parseCollModUUIDAndNss should uassert the input UUID is in the catalog

(cherry picked from commit e573d7f2f908f3fbe96716851cd1b1e3d65fe7c9)
Branch: v4.0
https://github.com/mongodb/mongo/commit/5d225d07531e9af99f532f03c8adb2502c7536a8

Comment by Githook User [ 24/May/18 ]

Author:

{'username': 'xy24', 'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com'}

Message: SERVER-34341 parseCollModUUIDAndNss should uassert the input UUID is in the catalog
Branch: master
https://github.com/mongodb/mongo/commit/e573d7f2f908f3fbe96716851cd1b1e3d65fe7c9

Comment by Xiangyu Yao (Inactive) [ 16/May/18 ]

Reopening this ticket and unlinking it with SERVER-33617 since the issue described in SERVER-33617 does not exist anymore and this ticket seems an improvement that we should do.

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