[SERVER-45205] Consider removing 'out.sharded' option from mapReduce command Created: 17/Dec/19  Updated: 06/Dec/22  Resolved: 07/Apr/20

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

Type: Task Priority: Major - P3
Reporter: James Wahlin Assignee: Backlog - Query Team (Inactive)
Resolution: Won't Fix Votes: 0
Labels: qopt-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-45210 Accept and ignore the nonAtomic:true ... Closed
Assigned Teams:
Query
Sprint: Query 2020-03-23, Query 2020-04-06
Participants:

 Description   

As of MongoDB 4.4 the "out.sharded" option to mapReduce is only accepted with a value of true but is ignored. This option was maintained for 4.4 to allow for a viable 4.2->4.4 upgrade path as 4.2 only allows writing to a sharded collection with out.sharded:true specified.

Once users are on 4.4 this flag no longer serves a purpose so we should remove for 4.6.



 Comments   
Comment by James Wahlin [ 04/Mar/20 ]

Before doing this work we will need to confirm that the Java driver no longer requires the ability to set "out.sharded: true" for the next release. See the commentary in SERVER-45210 for context.

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