[SERVER-12895] Temporary mapreduce collections should be created in the destination database Created: 25/Feb/14  Updated: 06/Dec/22  Resolved: 07/Mar/17

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

Type: Improvement Priority: Major - P3
Reporter: Mark Helmstetter Assignee: Backlog - Query Team (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Query
Participants:

 Description   

When running mapReduce in sharded environment, temporary collections are created within the source database, even if you specify a separate output database. When outputting to a collection in a separate database, it would be beneficial if those temporary collections could be created in that separate database.



 Comments   
Comment by Ian Whalen (Inactive) [ 24/Feb/17 ]

mark.helmstetter can you provide any additional info about why it's beneficial to do this on the destination database?

Generated at Thu Feb 08 03:29:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.