[
https://issues.apache.org/jira/browse/LUCENE-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889314#action_12889314
]
Uwe Schindler commented on LUCENE-2541:
---------------------------------------
The explanation (for changes):
The bug happens when the range covers abs(bounds)>2^31 and both bounds are
close together in the same range bracket (as Mike calls it). The problem is, as
yonik corrected, the exit condition, because the <-comparision is invalid for
all these numbers, because their signed longs are compares signed not unsigned.
Please let me also confirm that the solution is correct and embed the test in
my splitRange tests in TestNumericUtils. The bug is not inside NRQ, its the
underlying bit magic, so it should be added to TestNumericUtils.
> NumericRangeQuery errors with endpoints near long min and max values
> --------------------------------------------------------------------
>
> Key: LUCENE-2541
> URL: https://issues.apache.org/jira/browse/LUCENE-2541
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.9
> Reporter: Koji Sekiguchi
> Assignee: Uwe Schindler
> Attachments: LUCENE-2541.patch, LUCENE-2541.patch,
> TestNumericRangeQuery.java
>
>
> This problem first reported in Solr:
> http://lucene.472066.n3.nabble.com/range-query-on-TrieLongField-strange-result-tt970974.html#a970974
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
