[
https://issues.apache.org/jira/browse/SOLR-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513017#comment-14513017
]
David Smiley commented on SOLR-6741:
------------------------------------
This should definitely use Lucene's new & experimental "auto prefix terms";
Hoss mentioned that. This is *not* blocked by LUCENE-5596. We'd need a new
Solr field type with the sugar like in the IPv4 patch here but that which does
a range between 2 terms. That will functionally work even without "auto prefix
terms". Then configure the codec appropriately and then the search will be
much faster (and indexing a bit slower too of course).
FWIW Lucene spatial's NumberRangePrefixTreeStrategy could work, but it needs a
subclass of NumberRangePrefixTree and presently the only one that exists is
DateRangePrefixTree. _If_ you need to index IPv6 ranges, then this _should_ be
faster than intersecting 2 range queries on a start and end field.
> IPv6 Field Type
> ---------------
>
> Key: SOLR-6741
> URL: https://issues.apache.org/jira/browse/SOLR-6741
> Project: Solr
> Issue Type: Improvement
> Reporter: Lloyd Ramey
> Attachments: SOLR-6741.patch
>
>
> It would be nice if Solr had a field type which could be used to index IPv6
> data and supported efficient range queries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
