[LUCENE-38] RangeQuery without lower term and inclusive=false skips blank fields

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.9
• Component/s: core/search

Environment

Operating System: other
Platform: Other

• Bugzilla Id: 9782
• Assignee: Unassigned
• Reporter: Otis Gospodnetic
• Created: 11/Jun/02 22:02
• Updated: 28/Aug/22 11:10
• Resolved: 13/Nov/08 10:08

Description

This was reported by "James Ricci" <[e-mail]> at:
http://nagoya.apache.org/eyebrowse/ReadMsg?listName=[e-mail]&msgNo=1835

When you create a ranged query and omit the lower term, my expectation
would be that I would find everything less than the upper term. Now if I pass
false for the inclusive term, then I would expect that I would find all
terms less than the upper term excluding the upper term itself.

What is happening in the case of lower_term=null, upper_term=x,
inclusive=false is that empty strings are being excluded because
inclusive is set false, and the implementation of RangedQuery creates a default
lower term of Term(fieldName, ""). Since it's not inclusive, it excludes "".
This isn't what I intended, and I don't think it's what most people would
imagine RangedQuery would do in the case I've mentioned.

I equate lower=null, upper=x, inclusive=false to Field < x. lower=null,
upper=x, inclusive=true would be Field <= x. In both cases, the only
difference should be whether or not Field = x is true for the query.