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

Allow geoNear within a lookup pipeline in the sharded case

XMLWordPrintableJSON

    • Query
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • 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.  

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

              Created:
              Updated:
              Resolved: