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

Allow geoNear within a lookup pipeline in the sharded case

    XMLWordPrintable

Details

    • ALL

    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
          related to

          Task - A task that needs to be done. SERVER-43496 Complete TODO listed in SERVER-38995

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

          Task - A task that needs to be done. SERVER-44217 Complete TODO listed in SERVER-38995

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

          Activity

            People

              backlog-server-query Backlog - Query Team (Inactive)
              brigitte.lamarche@mongodb.com Brigitte Lamarche (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: