Hi,
Paul Elschot wrote:
This could be done, but since not all scorers will be TermScorers it
will be necessary to add a method to Scorer (or perhaps even to its
DocIdSetIterator superclass):
public abstract int estimatedDocFreq();
and implement this for all existing instances. TermScorer could
implement it without estimating.
For AND/OR/NOT such an estimation is straightforward but for
proximity queries it would be more of a guess.
I agree. Indeed, for proximity queries, it is more tricky. Maybe taking
the frequency of the rarest term in a PhraseQuery / SpanQuery could be a
not so bad predictor in general.
Regards.
--
Renaud Delbru
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
