lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] Updated: (LUCENE-2760) optimize spanfirstquery, spanpositionrangequery
Date Sun, 14 Nov 2010 21:31:13 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Muir updated LUCENE-2760:
--------------------------------

    Attachment: LUCENE-2760.patch

here's the patch, the SpanPositionCheckQuery now has logic similar to FilteredTermsEnum,
instead of returning a boolean true/false for whether a match is acceptable,
it can return YES, NO, NO_AND_ADVANCE


> optimize spanfirstquery, spanpositionrangequery
> -----------------------------------------------
>
>                 Key: LUCENE-2760
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2760
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Robert Muir
>             Fix For: 3.1, 4.0
>
>         Attachments: LUCENE-2760.patch
>
>
> SpanFirstQuery and SpanPositionRangeQuery (SpanFirst is just a special case of this),
are currently inefficient.
> Take this worst case example: SpanFirstQuery("the").
> Currently the code reads all the positions for the term "the".
> But when enumerating spans, once we have passed the allowable range we should move on
to the next document (skipTo)
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


Mime
View raw message