[
https://issues.apache.org/jira/browse/LUCENE-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244630#comment-13244630
]
Mike commented on LUCENE-3833:
------------------------------
Three thoughts:
1. Do we need to set a review flag, or are we waiting for something else to
get this in?
2. Ignoring when not a boolean makes sense to me.
3. I'd also advocate for ignoring when a non-integer. Better to fail silently
when queries don't make sense than to throw an error. (At least that's my
philosophy - don't know about Solr's.)
> 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
> Attachments: LUCENE-3833.patch
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
