[
https://issues.apache.org/jira/browse/LUCENE-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942369#comment-13942369
]
Michael McCandless commented on LUCENE-5489:
--------------------------------------------
bq. I also think this method should only be on QueryRescorer and not in the
interface?
Woops, right, I'll move it.
{quote}
I also wonder why you extract the IDs and Scores, I think you should clone the
scoreDocs array and sort that first. Then you can just sort the rescored
scoreDocs array and simply merge the scores. Once you are done you resort the
previously cloned array and we don't need to do all the auto boxing in that
hashmap and it's the same sorting we already do?
{quote}
I think this can wait? It's just an optimization (making the code more hairy
but a bit faster). I'll put a TODO...
> 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]
