[SERVER-38995] Allow geoNear within a lookup pipeline in the sharded case Created: 14/Jan/19 Updated: 27/Oct/23 Resolved: 21/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Brigitte Lamarche (Inactive) | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | open_todo_in_code, query-44-grooming, todo_in_code | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Query
|
||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
Currently, attempting to run a $lookup sub-pipeline with a geoNear within it will cause DocumentSourceGeoNear's getNext to be called, triggering an error. Part of this ticket will involve reactivating jstests/aggregation/sources/geonear/requires_geo_index.js and jstests/aggregation/sources/lookup/lookup_subpipeline_geonear.js for passthroughs with sharded collections. It will also involve changing the internal error code assertion #50144 to a MONGO_UNNREACHABLE. |
| Comments |
| Comment by Githook User [ 19/Nov/19 ] |
|
Author: {'username': 'jameswahlin', 'email': 'james.wahlin@mongodb.com', 'name': 'James Wahlin'}Message: |
| Comment by David Storch [ 21/Jun/19 ] |
|
This ticket pertains specifically to a task that must be done in order to support $lookup into a sharded collection. It is not actionable until we renew the sharded $lookup effort. Closing as Gone Away. |