You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2016/02/23 11:31:18 UTC
[jira] [Commented] (LUCENE-7043) add BigIntegerPoint and
InetAddressPoint to sandbox
[ https://issues.apache.org/jira/browse/LUCENE-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158679#comment-15158679 ]
Michael McCandless commented on LUCENE-7043:
--------------------------------------------
+1, this looks wonderful!
> add BigIntegerPoint and InetAddressPoint to sandbox
> ---------------------------------------------------
>
> Key: LUCENE-7043
> URL: https://issues.apache.org/jira/browse/LUCENE-7043
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Robert Muir
> Attachments: LUCENE-7043.patch, LUCENE-7043.patch
>
>
> We can now index 128-bit quantities, but still, making Fields for these is a bit of work: you have to do some numericutils sign-extension/sign-flipping magic for BigInteger quantities, deal with ipv4-mapped ipv6 addresses, etc.
> We can just provide some simple field types that also have static factory methods for exact match/ranges.
> The BigIntegerPoint is N-dimensional, so acts just like any other primitive, except its bigger (e.g. long long).
> InetAddressPoint is 1-dimensional by nature: of course you can have multiple values per field, thats different. Since we prefix-compress values, we can just map IPv4 addresses to IPv6 space and it works for both types. This is consistent with what InetAddress does itself anyway.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org