Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Gone away
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Querying
Labels:

Assigned Teams:

Query
Operating System:
ALL
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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.

depends on

SERVER-38716 fix $geoNear and $text within $lookup sub-pipeline

Closed

SERVER-38728 Allow pipeline with $lookup into a sharded collection to run on mongod

Closed

related to

SERVER-43496 Complete TODO listed in SERVER-38995

Closed

SERVER-44217 Complete TODO listed in SERVER-38995

Closed

Assignee:: Backlog - Query Team (Inactive)
Reporter:: Brigitte Lamarche (Inactive)
Participants:: Backlog - Query Team, Brigitte Lamarche, David Storch, Githook User
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jan 14 2019 09:07:12 PM UTC
Updated:: Oct 27 2023 08:43:04 PM UTC
Resolved:: Jun 21 2019 10:02:42 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates