[
https://issues.apache.org/jira/browse/LUCENE-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-5489:
---------------------------------------
Attachment: LUCENE-5489.patch
OK, new patch, folding in Simon's & Rob's feedback (thanks!), adding more tests.
I made an entirely abstract class Rescorer, and then a QueryRescorer subclass
that uses a Query to get the 2nd pass scores. In the future we can have other
sources of scores, e.g. an ExpressionRescorer.
> Add query rescoring API
> -----------------------
>
> Key: LUCENE-5489
> URL: https://issues.apache.org/jira/browse/LUCENE-5489
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 4.8, 5.0
>
> Attachments: LUCENE-5489.patch, LUCENE-5489.patch, LUCENE-5489.patch
>
>
> When costly scoring factors are used during searching, a common
> approach is to do a cheaper / basic query first, collect the top few
> hundred hits, and then rescore those hits using the more costly
> query.
> It's not clear/simple to do this with Lucene today; I think we should
> make it easier.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
