[SERVER-85017] M/R Agg Design: How will the command be translated to agg? Created: 27/Jun/19 Updated: 12/Jan/24 Resolved: 02/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | James Wahlin | Assignee: | Jacob Evans |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Sprint: | Query 2019-07-15 | ||||
| Participants: | |||||
| Description |
|
Propose an outline of how a map/reduce command will be translated into an aggregation. Will it just directly call the aggregation command after constructing some BSON request? Or will it enter at a lower level? What things will it skip if it does enter at a lower level? As part of this we should also consider how a distributed MapReduce will work. Should it enter through cluster_aggregate.cpp or utilize some of the same helpers in cluster_aggregation_planner.cpp and sharded_agg_helpers.cpp. |