Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use Double vs Int for geoNear parameters. #256

Open
Andrewangeta opened this issue Jan 15, 2021 · 0 comments
Open

Use Double vs Int for geoNear parameters. #256

Andrewangeta opened this issue Jan 15, 2021 · 0 comments
Labels
enhancement help wanted in progress

Comments

@Andrewangeta
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
The geoNear aggregate stage should accept Doubles for its parameters maxDistance, minDistance and distanceMultiplier.
This way if you're doing any division for converting between units of distance it's not just rounded out to 0 and it looks like no documents match.

Describe the solution you'd like
Replace the geoNear aggregate stage to accept Doubles vs Int for maxDistance, minDistance and distanceMultiplier

The existing implementation could also be marked as @depricated to prevent breaking changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement help wanted in progress
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Joannis @Andrewangeta