[LUCENE-9578] TermRangeQuery with empty string lower bound edge case

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: trunk, 8.6.3
• Fix Version/s: 8.7
• Component/s: core/search
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Christoph Büscher
• Created: 12/Oct/20 15:01
• Updated: 28/Aug/22 16:09
• Resolved: 16/Oct/20 17:21

Description

Currently a TermRangeQuery with the empty String ("") as lower bound and includeLower=false leads internally constructs an Automaton that doesn't match anything. This is unexpected expecially for open upper bounds where any string should be considered to be "higher" than the empty string.

I think "Automata#makeBinaryInterval" should be changed so that for an empty string lower bound and an open upper bound, any String should match the query regardless or the includeLower flag.

Issue Links

• links to: GitHub Pull Request #1976