[
https://issues.apache.org/jira/browse/LUCENE-9578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand resolved LUCENE-9578.
----------------------------------
Fix Version/s: 8.7
Resolution: Fixed
Thanks Christoph!
> TermRangeQuery with empty string lower bound edge case
> ------------------------------------------------------
>
> Key: LUCENE-9578
> URL: https://issues.apache.org/jira/browse/LUCENE-9578
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/search
> Affects Versions: trunk, 8.6.3
> Reporter: Christoph Büscher
> Priority: Minor
> Fix For: 8.7
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
