[SERVER-29255] CollectionOptions::validate() fails if a UUID is present. Created: 17/May/17  Updated: 30/Oct/23  Resolved: 17/May/17

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.5.8

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:
Related
is related to SERVER-27987 Store collection UUIDs in the databas... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2017-05-29
Participants:

 Description   

CollectionOptions started supporting an optional collection UUID in SERVER-27987. The collection UUID is generated by the server and is not permitted as part of the collection options when provided by a user (as opposed to reading the existing collection metadata using listCollections). This behavior is controlled by the CollectionOptions::ParseKind enumeration when calling CollectionOptions::parse().

CollectionOptions also supports validation by calling CollectionOptions::validate(). Currently, validate() will fail if the metadata contains a collection UUID.



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

Author:

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

Message: SERVER-29255 CollectionOptions with UUID passes validation
Branch: master
https://github.com/mongodb/mongo/commit/c5be5fa7124ab601144b03d80786dd5279066cb2

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