[SERVER-30713] make mapReduce on mongos send UUID for final output collection of first pass of mapReduce to shards Created: 17/Aug/17  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.5.11
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: LamontN, PM-1017
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-30669 mapReduce on mongos should pass UUID ... Closed
Assigned Teams:
Cluster Scalability
Backwards Compatibility: Fully Compatible
Participants:

 Description   

This is slightly lower priority than making mongos send the UUID for the final output collection of the second pass, because the final output collection of the first pass is a transient collection.

When we start using UUIDs, in the second pass, we will probably want shards to query the final output collection of the first pass by UUID, which will only work if they all have the same UUID.

It isn't a huge deal if this doesn't get into 3.6, though, because there are no backwards compatibility implications, as this is a UUID for a transient collection that is not meant to be visible to the user. It could be booted into the Collection Lifecycle (PM-85) project.


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