[
https://issues.apache.org/jira/browse/LUCENE-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15458383#comment-15458383
]
Tim Allison commented on LUCENE-7434:
-------------------------------------
Thank you for the clarification.
I think I got the {{minNumberShouldMatch}}, but let me know if I didn't.
Is there a substantive difference between {{maxSearchWindow}} and SpanNear's
{{slop}}?
I can see a small difference in that:
"a b c" with {{minNumberShouldMatch=2}} and {{slop=2}} should match this
x a x b x c x
but it wouldn't match
x a x x x c x
Whereas with a {{maxSearchWindow=5}}, there would be a hit on both.
> Add minNumberShouldMatch parameter to SpanNearQuery
> ---------------------------------------------------
>
> Key: LUCENE-7434
> URL: https://issues.apache.org/jira/browse/LUCENE-7434
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Reporter: Tim Allison
> Priority: Minor
> Attachments: AllPairsNearSpans20160902.patch
>
>
> On the user list, [~saar32] asked about a new type of SpanQuery that would
> allow for something like BooleanQuery's minimumNumberShouldMatch
> bq. Given a set of search terms (t1, t2, t3, ti), return all documents where
> in a sequence of x=10 tokens at least c=3 of the search terms appear within
> the sequence.
> I _think_ we can modify SpanNearQuery fairly easily to accommodate this.
> I'll submit a PR in the next few days.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
