[DOCS-16412] Investigate changes in SERVER-75557: Allow minDistance and maxDistance parameters in $geoNear pipeline stage to take expressions Created: 02/Oct/23 Updated: 13/Nov/23 Resolved: 08/Nov/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0, Server_Docs_20231113 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Sarah Simpers |
| Resolution: | Done | Votes: | 0 |
| Labels: | request | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 18 weeks, 2 days ago | ||||||||
| Story Points: | 2 | ||||||||
| Description |
|
Original Downstream Change Summary The aggregation stage $geoNear now allows the 'minDistance' and 'maxDistance' arguments to be constant expressions that evaluate to a number (previously only a double was allowed). Description of Linked TicketThe minDistance and maxDistance parameters are only allowed to be a constant numbers right now. We can loosen the restriction to allow any expression as long as they evaluate to a number https://www.mongodb.com/docs/manual/reference/operator/aggregation/geoNear/ |