[SERVER-58426] Add planning logic for $lookup Created: 12/Jul/21 Updated: 29/Oct/23 Resolved: 11/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ian Boros | 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: | QE 2022-02-07, QE 2022-02-21 | ||||||||
| Participants: | |||||||||
| Description |
|
We must add logic to the query planner for planning a $lookup. This involves examining the size of the collections involved and choosing the join algorithm (nlj or hashed) using the heuristic we agreed on here:
|
| Comments |
| Comment by Githook User [ 10/Feb/22 ] |
|
Author: {'name': 'Irina Yatsenko', 'email': 'irina.yatsenko@mongodb.com', 'username': 'IrinaYatsenko'}Message: Co-authored-by: Mihai Andrei <mihai.andrei@mongodb.com> |