[ https://issues.apache.org/jira/browse/LUCENE-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrien Grand updated LUCENE-6708: --------------------------------- Attachment: LUCENE-6708.patch Here is a patch. I also took opportunity of this change to reduce over-specialization of our 3 top-field collectors (non-scoring, scoring-no-max and scoring-max) by merging them into a single class. > TopFieldCollector sometimes calls Scorer.score() several times on the same doc > ------------------------------------------------------------------------------ > > Key: LUCENE-6708 > URL: https://issues.apache.org/jira/browse/LUCENE-6708 > Project: Lucene - Core > Issue Type: Improvement > Reporter: Adrien Grand > Assignee: Adrien Grand > Priority: Minor > Attachments: LUCENE-6708.patch > > > If the sort spec includes a sort field that needs scores, and if > trackDocScores or trackMaxScore is set, then TopFieldCollectors may compute > the score several times on the same document, once to check whether the hit > is competitive, and once to update maxScore or to set the score on the > ScoreDoc. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org