[SERVER-25137] aggregation with graph lookup into non-existent collection throws an error Created: 18/Jul/16 Updated: 19/Nov/16 Resolved: 25/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Charlie Swanson |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Query 2016-10-31 | ||||||||
| Participants: | |||||||||
| Description |
|
if "from" collection in aggregate $graphLookup stage does not exist, you get error 40106, "errmsg" : "from collection must have a unique _id index" |
| Comments |
| Comment by Charlie Swanson [ 25/Oct/16 ] | ||||||||||||
|
I'm closing this and marking the fixVersion as "3.3.11", since this was actually fixed as fallout of the work in | ||||||||||||
| Comment by Githook User [ 25/Oct/16 ] | ||||||||||||
|
Author: {u'username': u'cswanson310', u'name': u'Charlie Swanson', u'email': u'charlie.swanson@mongodb.com'}Message: | ||||||||||||
| Comment by Asya Kamsky [ 24/Oct/16 ] | ||||||||||||
|
Looks like this is fixed in master/3.4 rc:
| ||||||||||||
| Comment by Ian Whalen (Inactive) [ 25/Jul/16 ] | ||||||||||||
|
We don't think this is required for 3.4, but if we happen to fix it while adding support for $graphLookup on views then we'll also resolve this ticket. | ||||||||||||
| Comment by Asya Kamsky [ 18/Jul/16 ] | ||||||||||||
|
this happens even if the aggregate command is happening on non-existent collection (which normally just returns nothing). |