Implement better dependency tracking in DocumentSourceGeoNear

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Aggregation Framework
    • None
    • Query Optimization
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      As part of SERVER-35043, the implementation of the geoNear command is being transplanted into the aggregation system. The $geoNear stage has never been smart about computing its dependencies and assumes that it needs the entire document.

      We could be smarter about the dependencies for a pipeline that begins with $geoNear, however, we would have to be careful with preserving the $meta projections for the geoNear distance and geoNear point if necessary.

            Assignee:
            [DO NOT USE] Backlog - Query Optimization
            Reporter:
            Kyle Suarez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: