[SERVER-28531] Fix convert-to-capped to use new UUID Created: 28/Mar/17  Updated: 06/Dec/17  Resolved: 29/Mar/17

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

Type: Bug Priority: Major - P3
Reporter: Geert Bosch Assignee: Geert Bosch
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-27989 Add collection UUIDs to oplog entries Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage 2017-04-17
Participants:

 Description   

The convertToCapped operation is essentially a copy of (part of) the existing collection to a new collection, followed by a rename of that collection over the original collection. So, we should make sure to use a new UUID.



 Comments   
Comment by Githook User [ 29/Mar/17 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-28531 Fix convert-to-capped to use new UUID.
Branch: master
https://github.com/mongodb/mongo/commit/f7bed566056ba8cc13f765a1f8eb00c798ffc405

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