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.

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

getNearest does not support queries over the entire earth #5773

Open
rocketraman opened this issue May 17, 2016 · 1 comment
Open

getNearest does not support queries over the entire earth #5773

rocketraman opened this issue May 17, 2016 · 1 comment
Milestone

Comments

@rocketraman
Copy link
Contributor

Currently getNearest max_dist has a maximum value of approximately 8 million meters [1] .

If one is interested in using getNearest where the possible results can be any document (i.e. over the entire earth), with a slice to get the top-10, or similar logic, then it seems the only way to do that currently is via a full table scan:

.orderBy(r.row("location").distance(point))

cc: @danielmewes

[1] Note that the actual maximum value that can be passed to max_dist is not clear either -- if one uses the value returned in the error message when the value is too large, the same error happens again, presumably because the value used internally is something larger than the value passed.

@danielmewes danielmewes added this to the backlog milestone May 18, 2016
@danielmewes
Copy link
Member

This limitation is a bit hard to resolve with the way getNearest is currently implemented as far as I remember. Putting into backlog for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants