[SERVER-29914] Correctly propagate new UUID for renaming across databases Created: 28/Jun/17  Updated: 30/Oct/23  Resolved: 05/Jul/17

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

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

Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

buildscripts/resmoke.py --suites=replica_sets_jscore_passthrough  "--mongodSetParameters={enableCollectionUUIDs: 1}" jstests/core/rename7.js

Sprint: Storage 2017-07-10
Participants:

 Description   

When enabling collection UUIDs, and renaming collections across databases, correctly pass through the UUID from the oplog entry, so primary and secondary will maintain identical UUIDs.



 Comments   
Comment by Githook User [ 05/Jul/17 ]

Author:

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

Message: SERVER-29914 Fix message wording
Branch: master
https://github.com/mongodb/mongo/commit/f2fc0b194cac25c0cf3478d8ccfba61f44400772

Comment by Githook User [ 05/Jul/17 ]

Author:

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

Message: SERVER-29914 correctly progagate UUIDs for rename across dbs
Branch: master
https://github.com/mongodb/mongo/commit/896b45b7e8125cecea630458b5def039389fc194

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