[SERVER-44318] M/R Agg: Reject MapReduce commands which would create a new sharded collection Created: 30/Oct/19 Updated: 29/Oct/23 Resolved: 18/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mihai Andrei | Assignee: | Charlie Swanson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2019-11-18, Query 2019-12-02, Query 2019-12-16, Query 2019-12-30 |
| Participants: |
| Description |
|
For example, a mapReduce with output mode "merge" with "out.sharded" true, and the target collection not existing. |
| Comments |
| Comment by Githook User [ 18/Dec/19 ] |
|
Author: {'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com', 'username': 'cswanson310'}Message: |
| Comment by Charlie Swanson [ 18/Nov/19 ] |
|
This is more or less good to go, but waiting to patch build and burn in until we flip the switch, since my new test only passes in the new implementation and we should be close to that point. |