[SERVER-5005] error message is very cryptic if the sort index of MR does not exist Created: 17/Feb/12 Updated: 06/Dec/22 Resolved: 01/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MapReduce |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Antoine Girbal | Assignee: | Backlog - Query Optimization |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Participants: |
| Description |
|
> db.usages.mapReduce(map, reduce, options); sort : { timestamp: -1.0 }", |
| Comments |
| Comment by David Storch [ 18/Nov/20 ] |
|
Flagging for re-triage by the Query Optimization team. This looks very old, so I doubt that a similar problem exists now that the mapReduce command is implemented in terms of the aggregation subsystem. |