[SERVER-81802] $lookup serializes unresolved sub-pipeline Created: 03/Oct/23 Updated: 31/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Alyssa Clark | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | query-product-scope-2, query-product-urgency-2, query-product-value-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Optimization
|
||||||||
| Participants: | |||||||||
| Description |
|
When working on It appears that we do report optimizations made to the lookup stage in explain output by manually adding on absorbed unwind and match info. |
| Comments |
| Comment by David Storch [ 12/Oct/23 ] |
|
There are some technical questions (including one of feasibility) because we think that the current implementation resolves views and optimizes the inner pipeline once per document from the outer side. Achieving this may require producing a dummy pipeline for the express purpose of displaying the results of view resolution and optimization. Sending to product triage cc christopher.harris@mongodb.com |