[
https://issues.apache.org/jira/browse/LUCENE-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-6697:
---------------------------------------
Attachment: LUCENE-6697.patch
Another iteration, I think it's ready. I renamed the thing to RangeTree.
It turned out it was simple to support fast ranges over arbitrary byte[], by
requiring SortedSetDVs and just indexing the long ord value into the BKD tree
which is already designed to index long values.
This means range tree should be a fast (at search time) way to support range
filtering for values that need more than 64 bits, e.g. BigInteger, INET v6,
etc. (LUCENE-5596).
There are some things we could do to make indexing faster, e.g. a single
sequential scan over all points to fill the binary tree index values, avoid the
"copy over again to fixed width" step, etc., but I think we can do these
later...
> Use 1D KD tree for alternative to postings based numeric range filters
> ----------------------------------------------------------------------
>
> Key: LUCENE-6697
> URL: https://issues.apache.org/jira/browse/LUCENE-6697
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Attachments: LUCENE-6697.patch, LUCENE-6697.patch
>
>
> Today Lucene uses postings to index a numeric value at multiple
> precision levels for fast range searching. It's somewhat costly: each
> numeric value is indexed with multiple terms (4 terms by default)
> ... I think a dedicated 1D BKD tree should be more compact and perform
> better.
> It should also easily generalize beyond 64 bits to arbitrary byte[],
> e.g. for LUCENE-5596, but I haven't explored that here.
> A 1D BKD tree just sorts all values, and then indexes adjacent leaf
> blocks of size 512-1024 (by default) values per block, and their
> docIDs, into a fully balanced binary tree. Building the range filter
> is then just a recursive walk through this tree.
> It's the same structure we use for 2D lat/lon BKD tree, just with 1D
> instead. I implemented it as a DocValuesFormat that also writes the
> numeric tree on the side.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
