[
https://issues.apache.org/jira/browse/SOLR-11057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084868#comment-16084868
]
Tomás Fernández Löbbe edited comment on SOLR-11057 at 7/18/17 12:53 AM:
------------------------------------------------------------------------
Here is a patch that creates a MatchNoDocsQuery in those cases, similar to what
we do in the DV range query case. This is not an issue with Float/Double, but
it probably is with Dates. Will add a test for that too
was (Author: tomasflobbe):
Here us a patch that creates a MatchNoDocsQuery in those cases, similar to what
we do in the DV range query case. This is not an issue with Float/Double, but
it probably is with Dates. Will add a test for that too
> RangeQuery can overflow in PointFields when quering the type limits
> -------------------------------------------------------------------
>
> Key: SOLR-11057
> URL: https://issues.apache.org/jira/browse/SOLR-11057
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Tomás Fernández Löbbe
> Assignee: Tomás Fernández Löbbe
> Attachments: SOLR-11057.patch, SOLR-11057.patch
>
>
> This can happen when the upper limit of the range is the lowest value of the
> type or when the lower limit is the max value of the type. For example:
> {{q=field_i:{Integer.MAX_VALUE TO Integer.MAX_VALUE]}}. Note that this should
> not return any docs
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
