[SERVER-28976] Allow $geoNear on collections with more than one 2dsphere/2d index Created: 26/Apr/17  Updated: 06/Dec/22  Resolved: 26/Oct/17

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

Type: Improvement Priority: Major - P3
Reporter: Sergey Kazankov Assignee: Backlog - Query Team (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-31651 geoNear command and $geoNear agg stag... Closed
Assigned Teams:
Query
Participants:

 Description   

$geoNear command requires that a collection have at most only one 2d index and/or only one 2dsphere

I guess that mongodb implicitly takes location field from index. The problem is that I have two location fields in collection (border and center point). Both fields have 2dsphere index. I want to query only center points with $geoNear, but this limitation does not allow me to do this.



 Comments   
Comment by David Storch [ 26/Oct/17 ]

kazankov, we now have a specific fix for this problem planned in SERVER-31651, so I am going to close this ticket as a duplicate. Let me know if you have any questions or concerns.

Best,
Dave

Comment by Ramon Fernandez Marina [ 16/Jul/17 ]

Apologies for the delay in getting back to you kazankov. The "Backlog" fixversion for this ticket indicates that it is not currently scheduled for any development cycle, so unfortunately there's not an ETA for completion. Tickets in the Backlog get reviewed for scheduling decisions periodically, and when this ticket gets scheduled JIRA will send you email about it.

Regards,
Ramón.

Comment by Sergey Kazankov [ 04/Jul/17 ]

mark.agarunov
@Mark Agarunov , do you have news about this ticket? When can it be resolved?

Comment by Mark Agarunov [ 28/Apr/17 ]

Hello kazankov,

Thank you for the report. I've set the fixVersion to "Needs Triage" for this improvement to be scheduled against our currently planned work. Updates will be posted on this ticket as they happen.

Thanks,
Mark

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