Robert Muir created LUCENE-4198:
-----------------------------------
Summary: Allow codecs to index term impacts
Key: LUCENE-4198
URL: https://issues.apache.org/jira/browse/LUCENE-4198
Project: Lucene - Java
Issue Type: Sub-task
Components: core/index
Reporter: Robert Muir
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
