Add support for $lookup with `let`/`pipeline` form to aggregation [DATAMONGO-2467]

Shiv Jha-Mathur opened DATAMONGO-2467 and commented

Perform uncorrelated subqueries between two collections as well as allow other join conditions besides a single equality match:

{
   $lookup:
     {
       from: <collection to join>,
       let: { <var_1>: <expression>, …, <var_n>: <expression> },
       pipeline: [ <pipeline to execute on the collection to join> ],
       as: <output array field>
     }
}

---

Reference URL: https://docs.mongodb.com/master/reference/operator/aggregation/lookup/#join-conditions-and-uncorrelated-sub-queries

1 votes, 2 watchers

[spring-projects-issues]

Herman Bovens commented

I think this one deserves Major priority instead of Minor.  Uncorellated subqueries and multiple join conditions are just two possible uses, but there is more.  Not being able to use a pipeline for lookup leads to inefficient queries: instead of doing a $project operation inside the $lookup operation when not all fields of the target document are needed, people fall back to doing the projection after the lookup (or even not at all).  Limiting the number of fields has proven to be faster for me, definitely much faster if the index on the target collection that is used contains all of the projected fields

[keyzj]

Any update on this issue?