Use Double vs Int for geoNear parameters.
Andrewangeta opened this issue · comments
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.