lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Allison (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7434) Add minNumberShouldMatch parameter to SpanNearQuery
Date Fri, 02 Sep 2016 12:26:22 GMT


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

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

View raw message