[jira] [Resolved] (LUCENE-6388) Optimize SpanNearQuery

["Robert Muir (JIRA)" <ji...@apache.org>]

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

Robert Muir resolved LUCENE-6388.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 5.x
                   Trunk

For now the check is implemented via Terms.getPayloads() until LUCENE-6390 is fixed.

> Optimize SpanNearQuery
> ----------------------
>
>                 Key: LUCENE-6388
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6388
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Robert Muir
>             Fix For: Trunk, 5.x
>
>         Attachments: LUCENE-6388.patch
>
>
> After the big spans overhaul in LUCENE-6308, we can speed up SpanNearQuery a little more:
> * SpanNearQuery defaults to collectPayloads=true, but this requires a slower implementation, for an uncommon case. Use the faster no-payloads impl if the field doesn't actually have any payloads.
> * Use a simple array of Spans rather than List in NearSpans classes. This is iterated over often in the logic.



--
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