[SERVER-43354] Translate Error Messages For MapReduce Created: 16/Sep/19 Updated: 29/Oct/23 Resolved: 06/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jacob Evans | Assignee: | Mihai Andrei |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Query 2019-10-21, Query 2019-11-04, Query 2019-11-18 | ||||||||
| Participants: | |||||||||
| Description |
|
In the process of translating MapReduce to an Agg pipeline a number of correct errors may be thrown. Despite their correctness, they will be phrased in terms of an agg command which is likely to confuse the user. We should catch these errors and reformat them so they make sense in terms of the issued MR command. |
| Comments |
| Comment by Githook User [ 06/Nov/19 ] |
|
Author: {'name': 'Mihai Andrei', 'email': 'mihai.andrei@mongodb.com'}Message: |
| Comment by Nicholas Zolnierz [ 09/Oct/19 ] |
|
In particular, it would be good to handle the $out parse error when the target collection is sharded (17017). I am looking at adding tests for this scenario under |