[SERVER-46052] elemMatch in GeoNear query doesn't support indexes Created: 09/Feb/20 Updated: 27/Oct/23 Resolved: 07/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | 4.2.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dennis Smal' | Assignee: | Dmitry Agranat |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
I use this aggregation for my collection
and this indexes:
It seems that indexes doesn't work.
For testing I created new indexes
and launch command
This works fine. But If I use elemMatch inside geoNear indexes doesn't work. |
| Comments |
| Comment by Dmitry Agranat [ 07/Jul/20 ] |
|
We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, |
| Comment by Carl Champain (Inactive) [ 20/Feb/20 ] |
|
So far we were not able to recreate the described behavior. To help us understand your issue, can you please provide:
Thank you, |
| Comment by Carl Champain (Inactive) [ 13/Feb/20 ] |
|
Thanks for the report. Kind regards, |