[
https://issues.apache.org/jira/browse/LUCENE-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773461#comment-13773461
]
Michael McCandless commented on LUCENE-5232:
--------------------------------------------
I'm not sure we should do this.
Today, when doMaxScore is false and doScores is true, we only score those hits
that make it into the PQ, which is typically a very small subset of all hits.
When an app needs scores, I think it often does not need the maxScore.
Can we somehow remove specialization without losing this functionality?
Decouple the two ...
> Remove doMaxScore from indexsearcher, collector specializations, etc
> --------------------------------------------------------------------
>
> Key: LUCENE-5232
> URL: https://issues.apache.org/jira/browse/LUCENE-5232
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Robert Muir
> Fix For: 5.0
>
>
> I think we should just compute doMaxScore whenever doDocScores = true.
> This would remove 4 collector specializations and remove a boolean parameter
> from 4 indexsearcher methods.
> We can just do this in 5.0 I think.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
