[SERVER-38843] Mapreduce should not create collections with duplicate IDs Created: 04/Jan/19  Updated: 29/Oct/23  Resolved: 07/Jan/19

Status: Closed
Project: Core Server
Component/s: MapReduce
Affects Version/s: 3.6.9
Fix Version/s: 3.6.10

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto Assignee: Matthew Russotto
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
Participants:
Linked BF Score: 45

 Description   

If a mapreduce is run while downgrading to compatibility version 3.4 (but before UUIDs are removed), and the final output collection exists, the new temporary collection will have the same UUID as the old final output collection. We should clear the options.uuid field whenever we do not set it explicitly.



 Comments   
Comment by Githook User [ 07/Jan/19 ]

Author:

{'username': 'mtrussotto', 'email': 'matthew.russotto@10gen.com', 'name': 'Matthew Russotto'}

Message: SERVER-38843 Mapreduce should not create collections with duplicate IDs
Branch: v3.6
https://github.com/mongodb/mongo/commit/31c0c760bd0c72be658bdf91d280b4dc3cf90ea2

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