Overcoming MapReduce Geospatial $near query default limit of 100

[David D.]

Hi,

I'm trying to do a MapReduce based on a query that looks something
like this:

query : {'ll' : {'$near': [40.702,-73.990], '$maxDistance': .01}}

The problem is that it seems $near has a default of 100 results (as
described here: http://www.mongodb.org/display/DOCS/Geospatial+Indexing#GeospatialIndexing-Querying)

When I execute the mapreduce, this limit is confirmed in the dbres
("counts":{"input":100,"emit":100,"output":4})

For a normal query, the documentation says to change the limit for a
$near query using dot notation find({'ll' : {'$near':
[40.702,-73.990], '$maxDistance': .01}}).limit(20). But how do we do
that with a map reduce? We can't simply append .limit() to the object
in the mapreduce command object (at least I get an error), and the
'limit' parameter of the mapreduce command has no effect on the $near
query.

So how do we get around the 100 limit for $near with a mapreduce?

[Bernie Hackett]

There is a limit parameter for the mapreduce command but it doesn't
seem to help in this case. I've opened a server ticket for this issue:

https://jira.mongodb.org/browse/SERVER-3571

On Aug 10, 6:25 am, "David D." <da...@grandelabs.com> wrote:
> Hi,
>
> I'm trying to do a MapReduce based on a query that looks something
> like this:
>
> query : {'ll' : {'$near': [40.702,-73.990], '$maxDistance': .01}}
>
> The problem is that it seems $near has a default of 100 results (as

> described here:http://www.mongodb.org/display/DOCS/Geospatial+Indexing#GeospatialInd...)

[David D.]

Thanks, this is really important if what you're trying to do is count
a lot of data that might be nearby...maybe the number of location-
based comments nearby, etc.