[SERVER-44461] Re-enable map_reduce_invalid_output_collection.js for non-aggregation mapReduce Created: 06/Nov/19  Updated: 06/Dec/22  Resolved: 26/Nov/19

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

Type: Task Priority: Major - P3
Reporter: Jack Mulrow 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
related to SERVER-44864 Complete TODO listed in SERVER-44461 Closed
Assigned Teams:
Query
Participants:

 Description   

map_reduce_invalid_output_collection.js verifies a mapReduce merging to an already sharded collection will fail if that collection is not sharded by _id. For non-aggregation mapReduce, this relies on upserts without the full shard key being rejected (see SERVER-42916). SERVER-44382 allowed upserted documents in a sharded collection to have missing shard key fields, so the non-aggregation mapReduce cases in the test were disabled. They should be re-enabled after determining how mapReduce to a collection sharded by a key other than _id should behave.



 Comments   
Comment by Nicholas Zolnierz [ 26/Nov/19 ]

This will go away once we switch to the new implementation in SERVER-42511.

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