lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] [Updated] (LUCENE-2780) optimize spantermquery
Date Thu, 09 May 2013 23:06:00 GMT


Uwe Schindler updated LUCENE-2780:

    Fix Version/s:     (was: 4.3)
> optimize spantermquery
> ----------------------
>                 Key: LUCENE-2780
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/search
>            Reporter: Robert Muir
>             Fix For: 4.4
>         Attachments: LUCENE-2780.patch
> Looking at
> I saw a user building DisjunctionMaxQuery / BooleanQuery with SpanTermQuerys.
> I wonder if users know that doing this is much slower than just using TermQuery?
> I agree it makes little sense to use SpanTermQuery if you arent going to use it inside
a SpanNear etc,
> but on the other hand, I think its a little non-intuitive that it wouldnt be just as
fast in a case like this.
> I could see this complicating queryparsing etc for users that want to sometimes use positions
> SpanTermQuery is the same as TermQuery, except tf is computed as (#of spans * sloppyFreq(spanLength)
> For this case, #ofspans = tf and spanLength for a single term is always 1.
> Maybe we should optimize SpanTermQuery to return TermScorer, with just this special tf
> This would avoid reading positions for anyone that does this.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message