It's indeed working. As Robert suggested, it's in the sandbox more because
it's unclear if it is really needed than because it is unstable.
The few data points I have suggest that among the users for whom LongPoint
is not enough, there are more users who need unsigned 64 bits integers than
true 128 bits integers.
Le sam. 27 févr. 2021 à 11:20, Michael Kleen <mkleen@gmail.com> a écrit :
> Looking at TestBigIntegerPoint it seems to me that the core functionality
> of BigIntegerPoint
> is working. Is there any reason you would advise me for not using it ? Is
> there anything
> missing ?
>
> > On 26. Feb 2021, at 22:14, Robert Muir <rcmuir@gmail.com> wrote:
> >
> > It was added to the sandbox originally (along with InetAddressPoint for
> ip
> > addresses) and just never graduated from there:
> > https://issues.apache.org/jira/browse/LUCENE-7043
> >
> > The InetAddressPoint was moved to core because it seems pretty common
> that
> > people want to do range queries on IP hosts and so on. So it got love.
> >
> > Not many people need 128-bit range queries I suppose?
> >
> > On Fri, Feb 26, 2021 at 1:25 PM Michael Kleen <mkleen@gmail.com> wrote:
> >
> >> Hello,
> >>
> >> I am interested in using BigIntegerPoint. What is the reason that it is
> >> part of the sandbox ? Is it ready for use ?
> >>
> >> Many thanks,
> >>
> >> Michael
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: java-user-help@lucene.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>