[SERVER-45294] mapReduce can no longer create an output collection in a sharded cluster (4.3.2) Created: 23/Dec/19 Updated: 27/Oct/23 Resolved: 02/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MapReduce |
| Affects Version/s: | 4.3.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Shane Harvey | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
I noticed while working on
On 4.2 mapReduce can create the output collection regardless of if the database exists. |
| Comments |
| Comment by Shane Harvey [ 02/Jan/20 ] |
|
Thanks! Feel free to close this ticket however you like. I've already updated the Python driver's tests to always create the output database to workaround this change. |
| Comment by James Wahlin [ 02/Jan/20 ] |
|
shane.harvey the ability for mapReduce to write to a collection in a non-existent database has been removed for MongoDB 4.4. The mapReduce command now executes via the aggregation framework which disallows this for the $out and $merge stages. Users will be required to create the target database and optionally the collection and shard this collection if desired. |