[SERVER-21621] Piped query Created: 23/Nov/15 Updated: 23/Nov/15 Resolved: 23/Nov/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 3.0.7 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Yang | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
It would be great if collection.find() can support piped query like aggregation. Let me explain this in a scenario below. In a customer support team, if a customer's issue has been handled by an engineer before, it's desired that the same engineer should handle new issue raised by this customer. Currently, to achieve this, I'd have to do two queries: This is technically possible but have drawbacks: If a piped query is supported, then customer information can be produced and consumed within MongoDB internally. It should be more optimal in term of performance and client side coding. |
| Comments |
| Comment by Ramon Fernandez Marina [ 23/Nov/15 ] |
|
xuguoming@nexlabs.com, please take a look at the $lookup operator, for I think it provides the functionality you're looking for. Regards, |