lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] Updated: (LUCENE-2541) NumericRangeQuery errors with endpoints near long min and max values
Date Fri, 16 Jul 2010 22:49:50 GMT


Uwe Schindler updated LUCENE-2541:

    Attachment: LUCENE-2541-uwe.patch

Hi Yonik,

here the biginteger variant that works exactly as the old long-based variant (without your
extra checks). This is my favourite solution as it never overflows and we can maybe extend
the whole NumericRange to BigInteger :-) To reduce object creation, it uses a precalculated
(1<<shift) array. I had to change the logic a little bit as it was broken with precStep=Integer.MAX_VALUE

The tests pass, I did not test your additional test, but I think it should too.

I will test some range splits tomorrow on the solution you found but as far as i see without
trying out, it seem to not work.

> NumericRangeQuery errors with endpoints near long min and max values
> --------------------------------------------------------------------
>                 Key: LUCENE-2541
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Search
>    Affects Versions: 2.9
>            Reporter: Koji Sekiguchi
>            Assignee: Uwe Schindler
>         Attachments: LUCENE-2541-uwe.patch, LUCENE-2541-uwe.patch, LUCENE-2541.patch,
> This problem first reported in Solr:

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:
For additional commands, e-mail:

View raw message