[SERVER-22949] Remove default limit from $geoNear aggregation stage Created: 03/Mar/16  Updated: 19/Apr/22  Resolved: 19/Jun/18

Status: Closed
Project: Core Server
Component/s: Aggregation Framework, Geo
Affects Version/s: None
Fix Version/s: 4.1.1

Type: Improvement Priority: Major - P3
Reporter: Backlog - Query Team (Inactive) Assignee: Kyle Suarez
Resolution: Done Votes: 0
Labels: eng-s, neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-23466 $match should be moved into the query... Backlog
Documented
is documented by DOCS-11830 Docs for SERVER-22949: Remove default... Closed
Duplicate
is duplicated by SERVER-38236 $geoNear (aggregation) when $maxDista... Closed
Related
related to SERVER-65475 4.0.21 -> 4.2 Upgrade issue, mongos a... Closed
related to SERVER-14515 Remove default limit from geoNear ope... Closed
related to SERVER-18965 $geoNear output limit of 16mb Closed
Backwards Compatibility: Major Change
Sprint: Query 2018-06-04, Query 2018-06-18, Query 2018-07-02
Participants:

 Description   

The default limit for the $near/$nearSphere query operators was removed in SERVER-14515. For consistency, the default limit should also be removed from the $geoNear aggregation stage.



 Comments   
Comment by Githook User [ 19/Jun/18 ]

Author:

{'username': 'ksuarz', 'name': 'Kyle Suarez', 'email': 'kyle.suarez@mongodb.com'}

Message: SERVER-35043, SERVER-22949: move geoNear implementation into aggregation

This commit removes the geoNear command and moves its implementation
into the aggregation framework. Users should use the aggregate command
with a $geoNear stage.

The implementation rewrite additionally removes the limit in the
$geoNear aggregation stage. To limit the number of results, use a $limit
stage.
Branch: master
https://github.com/mongodb/mongo/commit/7bc7864fc042b69d36a88c6839c5dd5b4eb20693

Comment by Andy Schwerin [ 20/Apr/18 ]

If the limit doesn't currently lead to a top-k sort, eliminating the implicit default will not impact existing applications' performance, and so is probably safe from that perspective.

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