Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-38995

Allow geoNear within a lookup pipeline in the sharded case

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Querying
    • Labels:
      None

      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.  

        Attachments

          Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-38716 fix $geoNear and $text within $lookup sub-pipeline

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-38728 Allow pipeline with $lookup into a sharded collection to run on mongod

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: