[ https://issues.apache.org/jira/browse/LUCENE-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13969298#comment-13969298 ]
Adrien Grand commented on LUCENE-5596: -------------------------------------- bq. but those types like BigDecimal or BigInteger should maybe use precisionSteps of multiples than 8 only +1 Anything below would certainly be wasteful. bq. PrefixTermsTokenFilter / MultiTermQuery like NumericUtils.splitTerms() This sounds good! > 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 > Assignee: Uwe Schindler > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org