You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2015/01/15 16:07:34 UTC

[jira] [Created] (LUCENE-6184) BooleanScorer should better deal with sparse clauses

Adrien Grand created LUCENE-6184:
------------------------------------

             Summary: BooleanScorer should better deal with sparse clauses
                 Key: LUCENE-6184
                 URL: https://issues.apache.org/jira/browse/LUCENE-6184
             Project: Lucene - Core
          Issue Type: Improvement
            Reporter: Adrien Grand
            Assignee: Adrien Grand
            Priority: Minor
             Fix For: Trunk, 5.1


The way that BooleanScorer works looks like this:
{code}
for each (window of 2048 docs) {
  for each (optional scorer) {
    scorer.score(window)
  }
}
{code}

This is not efficient for very sparse clauses (doc freq much lower than maxDoc/2048) since we keep on scoring windows of documents that do not match anything. BooleanScorer2 currently performs better in those cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org