Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Use Lucene's query rescorer #6232
I just pushed a new commit for this. The bug that I referenced is fixed but there are several problems with the lucene APIs that I personally think it's not worth it unless lucene fixes it's APIs I had to do a lot of things on top that are really confusing IMO
We can fix the Lucene APIs: they are experimental. E.g. we can change it to do the rescoring "in-place", but I find this sort of strange. The full-resort after rescoring only a subset is odd because you're comparing apples to oranges at that point...
Alternatively, we could just add a utility API in Lucene on top of its existing APIs to do the in-place rescoring that ES wants, i.e. extract the topN from the first pass, rescore all of those, put back in and do a full resort.