Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: 4.1.1
Affects Version/s: None
Component/s: Aggregation Framework, Geo
Labels:
- eng-s
- neweng

Backwards Compatibility:
Major Change
Sprint:
Query 2018-06-04, Query 2018-06-18, Query 2018-07-02
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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.

is depended on by

SERVER-23466 $match should be moved into the query field of the $geoNear stage, where possible

Backlog

is duplicated by

SERVER-38236 $geoNear (aggregation) when $maxDistance = 0, return all locations

Closed

related to

SERVER-65475 4.0.21 -> 4.2 Upgrade issue, mongos adding limit geoNear queries, resulting in errors

Closed

SERVER-14515 Remove default limit from geoNear operations

Closed

SERVER-18965 $geoNear output limit of 16mb

Closed

Assignee:: Kyle Suarez (Inactive)
Reporter:: Backlog - Query Team (Inactive)
Participants:: Andy Schwerin, Backlog - Query Team, Githook User, Kyle Suarez
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Mar 03 2016 07:21:23 PM UTC
Updated:: Apr 19 2022 11:20:40 PM UTC
Resolved:: Jun 19 2018 03:45:01 AM UTC
Confidence Status Last Update:: 25/May/18 7:43 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates