[LUCENE-4198] Allow codecs to index term impacts

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 8.0
• Component/s: core/index
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Robert Muir
• Created: 05/Jul/12 20:34
• Updated: 28/Aug/22 13:21
• Resolved: 31/Jan/18 13:48

Description

Subtask of LUCENE-4100.

Thats an example of something similar to impact indexing (though, his implementation currently stores a max for the entire term, the problem is the same).

We can imagine other similar algorithms too: I think the codec API should be able to support these.

Currently it really doesnt: Stefan worked around the problem by providing a tool to 'rewrite' your index, he passes the IndexReader and Similarity to it. But it would be better if we fixed the codec API.

One problem is that the Postings writer needs to have access to the Similarity. Another problem is that it needs access to the term and collection statistics up front, rather than after the fact.

This might have some cost (hopefully minimal), so I'm thinking to experiment in a branch with these changes and see if we can make it work well.

Issue Links

• supercedes: LUCENE-8087 Record per-term max term frequencies
• supercedes: LUCENE-8083 Give similarities better values for maxScore
• links to: GitHub Pull Request #115