[SERVER-3571] $near query with limit > 100 only provides 100 input documents to map/reduce. Created: 10/Aug/11 Updated: 06/Dec/22 Resolved: 15/Mar/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MapReduce |
| Affects Version/s: | 1.9.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bernie Hackett | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Done | Votes: | 8 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Repro steps:
Output should look like this: Count of $near query results:
Results from map/reduce with limit(10):
Results from map/reduce with limit(500):
|
| Comments |
| Comment by David Storch [ 15/Mar/17 ] | |||||||||||||||||||||||||||||||||||||||||||
|
I'm resolving this ticket as Gone Away, since it is fixed in recent versions. Bernie's repro script produces the following output against a recent build of master:
The limit is now enforced correctly rather than defaulting to a limit of 100. I believe, but have not confirmed, that this was fixed under | |||||||||||||||||||||||||||||||||||||||||||
| Comment by Bernie Hackett [ 16/Aug/11 ] | |||||||||||||||||||||||||||||||||||||||||||
|
This is related to this mongodb-user post: https://groups.google.com/group/mongodb-user/browse_thread/thread/bcd99a391c78bac8?pli=1# | |||||||||||||||||||||||||||||||||||||||||||
| Comment by Bernie Hackett [ 16/Aug/11 ] | |||||||||||||||||||||||||||||||||||||||||||
|
mongodump of the repro database with geospatial index | |||||||||||||||||||||||||||||||||||||||||||
| Comment by Bernie Hackett [ 16/Aug/11 ] | |||||||||||||||||||||||||||||||||||||||||||
|
JS repro script. |