[SERVER-4341] disable non-default sort(), skip() and limit() together for geo queries Created: 21/Nov/11  Updated: 06/Dec/22  Resolved: 30/Jun/17

Status: Closed
Project: Core Server
Component/s: Geo
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Backlog - Query Team (Inactive)
Resolution: Won't Fix Votes: 5
Labels: 212push
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-3571 $near query with limit > 100 only pro... Closed
is related to SERVER-4247 allow non-geo fields to be first inde... Open
Assigned Teams:
Query
Operating System: ALL
Participants:

 Description   

... since the behavior is unexpected.



 Comments   
Comment by Ian Whalen (Inactive) [ 30/Jun/17 ]

Closing as Won't Fix based on Asya's most recent comment.

Comment by Asya Kamsky [ 24/Jun/17 ]

What's proposed would be backwards breaking change.

While the behavior may be desirable, perhaps it should be considered when we next have to add new version of geo indexes and disable this behavior on them only, with appropriate documentation.

To call attention to the issue without breaking existing applications, we could add a warning to the logs (plus some kind of assert - uassert) that indicates that suboptimal query was requested.

Comment by Asya Kamsky [ 24/Jun/17 ]

We cannot disable limit that's less than the default.

As long as it is <100 it works correctly and as expected.

Generated at Thu Feb 08 03:05:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.