Correct $maxDistance location for geoJSON $near queries. #664
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per
http://docs.mongodb.org/manual/release-notes/2.6-compatibility/#maxdistance-changes
$maxDistance must now be located within the $near operator on geoJSON objects,
not outside (as of mongoDB 2.6).
Note that this fix is backwards compatible with prior mongo releases as
geoJSON $near has always supported $maxDistance.