[SERVER-10797] MapReduce ignores 'sharded' option when connected to mongod Created: 17/Sep/13  Updated: 06/Dec/22  Resolved: 09/Mar/20

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

Type: Bug Priority: Minor - P4
Reporter: Phillip Quiza Assignee: Backlog - Query Team (Inactive)
Resolution: Done Votes: 0
Labels: 26qa, query-44-grooming
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Query
Operating System: ALL
Participants:

 Description   

db.coll.mapReduce(map, reduce, { out: { replace: outColl, sharded: true } });

The result of the above mapReduce operation is written to an unsharded collection on the connected shard. Should instead abort operation and display a message telling the user to run mapReduce with sharded option on mongos.



 Comments   
Comment by Charlie Swanson [ 09/Mar/20 ]

As part of a recent project where we created a new implementation for mapReduce based on the aggregation framework, the 'sharded' option has now become unnecessary. We continue to accept it for compatibility for now, but aren't planning on changing anything else about it at this time.

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