[CSHARP-1006] Consider implementing client side joins in LINQ queries Created: 26/Jun/14 Updated: 01/Apr/19 Resolved: 01/Apr/19 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | Linq |
| Affects Version/s: | 1.9.1 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | Robert Stam | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
So far one of our principles for LINQ support has been to not support any LINQ queries that would involve major client side processing or unexpected network traffic. The reason for this decision is that we don't want to make it easy to write simple looking LINQ queries that have surprising (in a bad way) performance characteristics. The counter argument is that sometimes an application has to do a client side join, and we might as well make it easier to do when you need to. The performance implications of client side joins could be carefully documented to help avoid surprises. |
| Comments |
| Comment by Jeffrey Yemin [ 01/Apr/19 ] |
|
Now that the server supports $lookup with a pipeline, there's no need to do do client-side joins. |