lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Saar Carmi (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LUCENE-7434) Add minNumberShouldMatch parameter to SpanNearQuery
Date Sun, 04 Sep 2016 19:50:21 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15463412#comment-15463412
] 

Saar Carmi edited comment on LUCENE-7434 at 9/4/16 7:49 PM:
------------------------------------------------------------

If I get it right, this is a minor difference. For my case it should be fine.


was (Author: saar32):
If I get it right, this is a minor difference. For my case it should be find.

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message