[DOCS-6169] Multiple near opration Created: 09/Sep/15  Updated: 03/Nov/17  Resolved: 02/Aug/16

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Bug Priority: Major - P3
Reporter: Docs Collector User (Inactive) Assignee: Sev Kozak
Resolution: Won't Fix Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Mongodb 3.0.4

Location: https://www.mongodb.org/about/support/
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0
Referrer: http://osdir.com/ml/mongodb-user/2015-02/msg00656.html
Screen Resolution: 1366 x 768
repo: mongodb-www-about
source: support


Participants:
Days since reply: 7 years, 28 weeks, 1 day ago

 Description   

A user has two addresses (one "pickup address" and one "delivery address").
The user wants to find other users which have similar pickup AND delivery addresses (this is why I need two $geoNear).

Example data (simplified):

User, pickup address, delivery address:
User 1, Germany, USA
User 2, France, Spain
User 3, Germany, USA
User 4, Germany, France
User 5, Canada, USA
User 6, Germany, USA

If user 1 wants to find other users, user 3 and user 6 have to be shown (because only there both addresses are "near").

In my real project the data is a bit more complex and of course I have real addresses (with latitude and longitude).

If two $geoNear are not possible, I could go first for the pickup address, then for the delivery address. However I fear a bad performance here because I have millions of addresses.

Need more details? Please let me know.



 Comments   
Comment by Kay Kim (Inactive) [ 02/Aug/16 ]

Apologies for the delay. I believe stackoverflow would be the more appropriate forum for your question as well as provide a more timely response.

DOCS JIRA project is for reporting problems, requesting enhancements to the documentation.

Closing this ticket.

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