[LUCENE-3609] BooleanFilter changed behavior in 3.5, no longer acts as if "minimum should match" set to 1

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.5
• Fix Version/s: 3.6, 4.0-ALPHA
• Component/s: core/search
• Lucene Fields: New
• Assignee: Uwe Schindler
• Reporter: Shay Banon
• Created: 29/Nov/11 19:20
• Updated: 28/Aug/22 13:02
• Resolved: 30/Nov/11 11:09

Description

The change LUCENE-3446 causes a change in behavior in BooleanFilter. It used to work as if minimum should match clauses is 1 (compared to BQ lingo), but now, if no should clauses match, then the should clauses are ignored, and for example, if there is a must clause, only that one will be used and returned.

For example, a single must clause and should clause, with the should clause not matching anything, should not match anything, but, it will match whatever the must clause matches.

The fix is simple, after iterating over the should clauses, if the aggregated bitset is null, return null.