[SERVER-23466] $match should be moved into the query field of the $geoNear stage, where possible Created: 01/Apr/16  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: Benjamin Murphy Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 0
Labels: perfomance, query-44-grooming
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-22949 Remove default limit from $geoNear ag... Closed
Duplicate
is duplicated by SERVER-4506 aggregation: optimize by pushing mat... Closed
Assigned Teams:
Query Optimization
Backwards Compatibility: Fully Compatible
Sprint: Query 12 (04/04/16)
Participants:

 Description   

As part of SERVER-4506, the $geoNear stage accepts a 'query' parameter which is an additional filter to apply to results returned from the geoNear. In a pipeline that has a $geoNear stage followed by a $match stage, we should set the query parameter of the geoNear to the $match, which pushes the matching logic down into the query subsystem.


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