[DOCS-8965] Query parser does not correctly handle geonear predicates with other predicates in the same field Created: 28/Sep/16  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Emily Hall Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-19783 Query parser does not correctly handl... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

We should allow queries such as

a: { $near: ..., $within: ... }

, but geonear predicates cannot be combined with other predicates in the same field, so we have to do for example,

$and: [ { a: { $near:... } }, { a: { $within: ... } } ]

. Also, ordering shouldn't matter.

In addition, for legacy formats for geonear queries, currently ordering matters and is incorrect in that for example,

a: { $eq: ..., $near: ..., $maxDistance: ... }

would error, but

a: { $near: ..., $eq: ..., $maxDistance: ... }

would ignore the $eq.



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 07:57:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.