[SERVER-23180] array in $lookup localField should not be interpreted literally Created: 16/Mar/16 Updated: 16/Mar/16 Resolved: 16/Mar/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
In $lookup if the value of localField is an array, we try to use it as a literal array to match foreignField. That seems wrong (or at least not useful). It should instead use the content of the array field as $in in the lookup rather than $eq. |
| Comments |
| Comment by David Storch [ 16/Mar/16 ] |
|
charlie.swanson asya, yep, resolving as a dup. |
| Comment by Charlie Swanson [ 16/Mar/16 ] |
|
If I understand this correctly, it's a dup of |