[LUCENE-7621] Per-document minShouldMatch

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 7.1, 8.0
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Adrien Grand
• Created: 05/Jan/17 16:10
• Updated: 28/Aug/22 15:08
• Resolved: 21/Aug/17 09:54

Description

I have seen similar requirements a couple times but could not find any related issue so I am opening one now. The idea would be to allow passing a LongValuesSource rather than an integer as the minShouldMatch parameter of BooleanQuery so that the number of required clauses can depend on the document that is being matched. In terms of implementation, it looks like it would be straightforward as we would just have to update the value of minShouldMatch in MinShouldMatchSumScorer.setDocAndFreq and things would still be efficient, ie. we would still use advance on the costly clauses.

This kind of feature would allow to run queries that must match eg. 80% of the terms that a document contains (by indexing the number of terms in a separate field). It would also make it possible for Luwak or ES' percolator to index boolean queries that have a value of minShouldMatch greater than 1 more efficiently.

I do not have any plans to work on it soon but I am curious how much interest this feature would drive.

Issue Links

• is related to: SOLR-12673 Superset Query
• is related to: LUCENE-7148 Support boolean subset matching
• links to: a use case for boolean expression matching