Fix "near" aggregation operator input type #12954
Merged
+9
−9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@vkarpov15 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
The current input parameter type for
nearaggregation operator does not reflect what MongoDB actually supports since version4.0(https://www.mongodb.com/docs/v4.0/reference/operator/aggregation/geoNear/).4.0is minimum supported version by Mongoose^6.0.0(https://mongoosejs.com/docs/compatibility.html).I've switched to the correct (already existing) interface, removed
uniqueDocsproperty (which has no effect since MongoDB2.6) and addednumproperty supported in MongoDB4.0.xbut removed in4.2.Examples
Without these changes, I cannot, for example, use GeoJSON point:
