[
https://issues.apache.org/jira/browse/LUCENE-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe resolved LUCENE-7111.
--------------------------------
Resolution: Fixed
Fix Version/s: 5.6
5.5.2
> DocValuesRangeQuery.newLongRange behaves incorrectly for Long.MAX_VALUE and
> Long.MIN_VALUE
> ------------------------------------------------------------------------------------------
>
> Key: LUCENE-7111
> URL: https://issues.apache.org/jira/browse/LUCENE-7111
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/search
> Reporter: Ishan Chattopadhyaya
> Assignee: Steve Rowe
> Fix For: 6.1, 5.5.2, master (7.0), 5.6, 6.0
>
> Attachments: LUCENE-7111.patch, LUCENE-7111.patch, LUCENE-7111.patch
>
>
> It seems that the following queries return all documents, which is unexpected:
> {code}
> DocValuesRangeQuery.newLongRange("dv", Long.MAX_VALUE, Long.MAX_VALUE, false,
> true);
> DocValuesRangeQuery.newLongRange("dv", Long.MIN_VALUE, Long.MIN_VALUE, true,
> false);
> {code}
> In Solr, floats and doubles are converted to longs and -0d gets converted to
> Long.MIN_VALUE, and queries like {-0d TO 0d] could fail due to this,
> returning all documents in the index.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
