[
https://issues.apache.org/jira/browse/LUCENE-6881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998823#comment-14998823
]
Michael McCandless commented on LUCENE-6881:
--------------------------------------------
bq. Curious; do you imagine that BKD might one day be modified to differentiate
the indexed cells by two types
I do think that's a natural (future!) generalization for {{DimensionalFormat}},
so we can index shapes.
It's useful in the 1D case as well: it would let us index numeric ranges, or
even unions of disjoint ranges, in a single document/field.
But I think we should postpone this for now ... it would add quite a bit of
complexity, and we need to see how dimensional values are used / hardened first.
> Cutover all BKD tree implementations to the codec
> -------------------------------------------------
>
> Key: LUCENE-6881
> URL: https://issues.apache.org/jira/browse/LUCENE-6881
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: Trunk
>
> Attachments: LUCENE-6881.patch, LUCENE-6881.patch
>
>
> This is phase 4 for enabling indexing dimensional values in Lucene
> ... follow-on from LUCENE-6861.
> This issue removes the 3 pre-existing specialized experimental BKD
> implementations (BKD* in sandbox module for 2D lat/lon geo, BKD3D* in
> spatial3d module for 3D x/y/z geo, and range tree in sandbox module)
> and instead switches over to having the codec index the dimensional
> values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
