[SERVER-7906] geoNear command doesn't work on sharded 2dsphere index Created: 11/Dec/12  Updated: 11/Jul/16  Resolved: 12/Dec/12

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

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: hari.khalsa@10gen.com
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File test.js    
Operating System: ALL
Participants:

 Description   

See attached test.



 Comments   
Comment by auto [ 13/Dec/12 ]

Author:

{u'date': u'2012-12-13T18:37:27Z', u'email': u'hkhalsa@10gen.com', u'name': u'Hari Khalsa'}

Message: SERVER-7906 fix sharded geonear test
Branch: master
https://github.com/mongodb/mongo/commit/98f016e8cfc74b4a6db9aa9265af2f5a7ab05d75

Comment by auto [ 12/Dec/12 ]

Author:

{u'date': u'2012-12-12T19:52:20Z', u'email': u'hkhalsa@10gen.com', u'name': u'Hari Khalsa'}

Message: SERVER-7906 fix sharded geonear
Branch: master
https://github.com/mongodb/mongo/commit/9783afcb785f4fe6d90377b84a895632e83a4388

Comment by hari.khalsa@10gen.com [ 11/Dec/12 ]

I suspect this file has something to do with it:

src/mongo/s/commands_public.cpp

I think this sends it out to the shards and assumes some behavior that 2dsphere near doesn't do, probably some variable not returned in status...

Will take a look/fix tmmw.

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