lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Rowe (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (LUCENE-7111) DocValuesRangeQuery.newLongRange behaves incorrectly for Long.MAX_VALUE and Long.MIN_VALUE
Date Mon, 21 Mar 2016 13:03:25 GMT

     [ 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: 6.1
                   master

Thanks Ishan!

> 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: master, 6.0, 6.1
>
>         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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message