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

LUCENE-8952: Use a sort key instead of true distance in NearestNeighbor. #832

Merged
merged 3 commits into from
Aug 23, 2019
Merged

LUCENE-8952: Use a sort key instead of true distance in NearestNeighbor. #832

merged 3 commits into from
Aug 23, 2019

Commits on Aug 14, 2019

  1. LUCENE-8952 Use a sort key instead of true distance in NearestNeighbors. 

    This commit addresses a TODO in NearestNeighbors around switching to
`SloppyMath.haversinSortKey`. When comparing candidate hits, we now only compute
a distance sort key. The sort key is converted to a true distance when returning
the final set of `FieldDocs`.
    @jtibshirani
    jtibshirani committed Aug 14, 2019
    Configuration menu
    Copy the full SHA
    4df26cc View commit details
    Browse the repository at this point in the history

Commits on Aug 23, 2019

  1. Also use a sort key for the best cell distance.

    @jtibshirani
    jtibshirani committed Aug 23, 2019
    Configuration menu
    Copy the full SHA
    cc95ecd View commit details
    Browse the repository at this point in the history

  2. Add a changelog entry.

    @jtibshirani
    jtibshirani committed Aug 23, 2019
    Configuration menu
    Copy the full SHA
    81cfaaf View commit details
    Browse the repository at this point in the history