[DOCS-4995] Modify $nearSphere documentation to be in line with $near for sharded collections Created: 13/Mar/15 Updated: 30/Oct/23 Resolved: 26/Mar/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andre de Frere | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | geo | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 8 years, 47 weeks ago | ||||||||
| Description |
|
both $near and $nearSphere have the same behaviour for sharded collections:
However, this is not denoted in the documentation for $nearSphere (only $near, as above). Running $nearSphere on a sharded collection will result in:
|
| Comments |
| Comment by Kay Kim (Inactive) [ 26/Mar/15 ] |