[SERVER-75979] Consider parameterizing the $lookup inner pipeline at the optimization phase, not execution phase Created: 11/Apr/23 Updated: 26/May/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Yoon Soo Kim | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | query-product-scope-2, query-product-urgency-3, query-product-value-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Query Optimization
|
||||
| Participants: | |||||
| Linked BF Score: | 4 | ||||
| Description |
|
The more fundamental issue that caused BF-28050 is that we repeatedly parse and optimize the $lookup inner pipeline for each input document, not parameterizing the inner pipeline. The classic $lookup would be used in foreseeable future given that the Nebari $lookup (hash lookup) does not support $lookup with inner pipeline and even though the Nebari $lookup supports $lookup with inner pipeline, it may take a while until we can fully switch to Nebari. Hope we could address this issue sooner or later. |