Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Wed, 29 Feb 2012 02:35:57 +0000 (UTC)
From: "Hoss Man (Updated) (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <829970342.1155.1330482957331.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1143764016.624.1328495879604.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (LUCENE-3833) Add an operator to query parser for
 term quorum (ie: BooleanQuery.setMinimumNumberShouldMatch)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hoss Man updated LUCENE-3833:
-----------------------------

    Summary: Add an operator to query parser for term quorum (ie: BooleanQuery.setMinimumNumberShouldMatch)  (was: Add an operator to edismax for term quorum)

Moved issue from Solr to Lucene since it should really be dealt with in the underlying query parser(s).

I would suggest that the "~" syntax makes more sense then "/" for this (ie: {{ A AND (B C D)~2}} since...

* "/" was recently added to the query parser as a metacharacter for "quoting" regex queries and the extremely different meanings might confuse people
* "~" already serves nearly the same purpose for phrases (slop) and fuzzy queries (amount of fuzziness) ... it seems a natural way to express "how many" of the clauses you want to match.
                
> Add an operator to query parser for term quorum (ie: BooleanQuery.setMinimumNumberShouldMatch)
> ----------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-3833
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3833
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: core/queryparser
>            Reporter: Mike
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> A project I'm working on requires *term quorum* searching with stemming turned off. The users are accostomed to Sphinx search, and thus expect a query like [ A AND (B C D)/2 ] to return only documents that contain A or at least two of B, C or D. 
> So this document would match:
> a b c
> But this one wouldn't:
> a b
> This can be a useful form of fuzzy searching, and I think we support it via the MM parameter, but we lack a user-facing operator for this. It would be great to add it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org