Remove ScoringNoMaxScoreCollector [LUCENE-6219]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
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.
---
Migrated from [LUCENE-6219](https://issues.apache.org/jira/browse/LUCENE-6219) by Adrien Grand (@jpountz), updated May 09 2016
Attachments: [LUCENE-6219.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-6219/LUCENE-6219.patch)
Contributor guide
Assessment
This issue has not been assessed yet.