[
https://issues.apache.org/jira/browse/LUCENE-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13969258#comment-13969258
]
Robert Muir commented on LUCENE-5596:
-------------------------------------
Hey, looks like a pretty thorough job here. Do you think BigNumericTokenStream
should be combined with NumericTokenStream or kept separate? Maybe instead of
NumericTokenStream working with longs in its setter (only for the attributeimpl
to convert to bytes), it should just do that up front so it can work with
BigInteger too?
Do you think the fieldcache impl should instead just act like a filtered
BinaryDocValues (BytesRef api) instead of a BigInteger[]? This would allow it
to just use a large paged byte[] instead of holding millions of biginteger
objects. This would work fine for sorting too right (just compare bytes) ?
Maybe [~thetaphi] can take a look when he gets some time.
> Support for index/search large numeric field
> --------------------------------------------
>
> Key: LUCENE-5596
> URL: https://issues.apache.org/jira/browse/LUCENE-5596
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: Kevin Wang
> Attachments: LUCENE-5596.patch, LUCENE-5596.patch
>
>
> Currently if an number is larger than Long.MAX_VALUE, we can't index/search
> that in lucene as a number. For example, IPv6 address is an 128 bit number,
> so we can't index that as a numeric field and do numeric range query etc.
> It would be good to support BigInteger / BigDecimal
> I've tried use BigInteger for IPv6 in Elasticsearch and that works fine, but
> there are still lots of things to do
> https://github.com/elasticsearch/elasticsearch/pull/5758
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
