[
https://issues.apache.org/jira/browse/LUCENE-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889507#action_12889507
]
Yonik Seeley commented on LUCENE-2541:
--------------------------------------
bq. Which patch do you prefer?
Look at the size difference in code changes... it's no contest ;-)
I also did a quick performance test of splitRange with 1M random bounds.
patch with longs: 250ms (and no garbage creation)
patch with BigInts: 11714ms (and a lot of garbage creation)
BigInts was 46x slower.
> 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
> Fix For: 2.9.4, 3.0.3, 3.1, 4.0
>
> Attachments: LUCENE-2541-uwe-BigDecimal.patch,
> LUCENE-2541-uwe-longs.patch, LUCENE-2541-uwe.patch, LUCENE-2541-uwe.patch,
> 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: [email protected]
For additional commands, e-mail: [email protected]
