[
https://issues.apache.org/jira/browse/LUCENE-6580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593173#comment-14593173
]
Alan Woodward commented on LUCENE-6580:
---------------------------------------
This is because slops mean different things between the two queries. In
PhraseQuery, a slop of greater than 0 means we end up with a SloppyPhraseScorer
that relaxes the ordering constraint (so you can have, in effect, the 'gap'
appearing after the end of the match). An ordered SpanNearQuery with a slop,
however, still requires its clauses to be in order, but allows them to be
spaced out.
So this issue makes an ordered SpanNearQuery more like a PhraseQuery only in
the case that the PQ has defined gaps, but zero slop.
> Allow defined-width gaps in SpanNearQuery
> -----------------------------------------
>
> Key: LUCENE-6580
> URL: https://issues.apache.org/jira/browse/LUCENE-6580
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Alan Woodward
> Attachments: LUCENE-6580.patch, LUCENE-6580.patch
>
>
> SpanNearQuery is not quite an exact Spans replacement for PhraseQuery at the
> moment, because while you can ask for an overall slop in an ordered match,
> you can't specify exactly where the gaps should appear.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
