[SERVER-35424] Implement better dependency tracking in DocumentSourceGeoNear Created: 05/Jun/18  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Kyle Suarez Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Optimization
Participants:

 Description   

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.


Generated at Thu Feb 08 04:39:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.