[SERVER-29072] Add support for $lookup into a sub-pipeline Created: 04/May/17 Updated: 30/Oct/23 Resolved: 19/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | James Wahlin | Assignee: | James Wahlin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Major Change | ||||||||||||||||||||||||||||||||||||||||
| Sprint: | Query 2017-05-29 | ||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||
| Description |
|
Extend command syntax to allow for "pipeline" field as an alternative to localField/foreignField |
| Comments |
| Comment by henry clifford [ 01/Dec/17 ] | ||||||||||||||||||||||||||||
|
thanks James! | ||||||||||||||||||||||||||||
| Comment by James Wahlin [ 01/Dec/17 ] | ||||||||||||||||||||||||||||
|
Hi henry@live.xyz, As of our latest 3.6 release candidate, an equality join using $expr will not make use of indexes, which is likely the cause of the performance differential you see. We are working on adding index use for equality join under Best, | ||||||||||||||||||||||||||||
| Comment by henry clifford [ 01/Dec/17 ] | ||||||||||||||||||||||||||||
|
is there a way to get similar performance when using the pipeline syntax to the more traditional local/foreignField? there is a very large perf difference between
and the pipeline syntax (using $expr as recommended by the docs)
this example is intentionally simplified thanks! | ||||||||||||||||||||||||||||
| Comment by Githook User [ 19/May/17 ] | ||||||||||||||||||||||||||||
|
Author: {u'username': u'jameswahlin', u'name': u'James Wahlin', u'email': u'james.wahlin@10gen.com'}Message: |