[SERVER-14329] 2d queries with skip and limit don't behave as expected Created: 20/Jun/14 Updated: 10/Dec/14 Resolved: 07/Jul/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo |
| Affects Version/s: | 2.6.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Doron Pagot | Assignee: | Siyuan Zhou |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
|||||||||
| Operating System: | ALL | |||||||||
| Steps To Reproduce: | to reproduce (in mongo client):
returns:
when you
there's nothing. |
|||||||||
| Participants: | ||||||||||
| Description |
|
when you skip '2d' geo queries, the limit starts from the start and not from the skip. for example, skip 100, limit 1 will always return nothing, but skip 100, limit 101 will return a single value (if exists) |
| Comments |
| Comment by Doron Pagot [ 20/Jun/14 ] |