You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2015/02/04 19:47:35 UTC

[jira] [Commented] (LUCENE-6219) Remove ScoringNoMaxScoreCollector

    [ https://issues.apache.org/jira/browse/LUCENE-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305710#comment-14305710 ] 

Adrien Grand commented on LUCENE-6219:
--------------------------------------

Looks like this somehow supersedes LUCENE-5232 by removing a collector. But this patch is different in the sense that it keeps the functionality: you can still have scores on the top docs and it will be faster than tracking the maximum score.

> Remove ScoringNoMaxScoreCollector
> ---------------------------------
>
>                 Key: LUCENE-6219
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6219
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Adrien Grand
>            Assignee: Adrien Grand
>            Priority: Minor
>             Fix For: Trunk, 5.1
>
>         Attachments: LUCENE-6219.patch
>
>
> ScoringNoMaxScoreCollector does like NonScoringCollector except that it computes the score for all competitive hits in order to have the score set on the final top hits.
> This is inefficient since there are potentially many more competitive documents than the requested number of hits, especially if the index order is not random. We could instead compute the top hits with NonScoringCollector and then compute scores on these top hits only. Another nice side-effect is that it would help get rid of a TopFieldCollector specialization.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org