[
https://issues.apache.org/jira/browse/LUCENE-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032700#comment-17032700
]
ASF subversion and git services commented on LUCENE-9149:
---------------------------------------------------------
Commit 206a70e7b79050db0d351135e406cfb997cbeee1 in lucene-solr's branch
refs/heads/master from Nicholas Knize
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=206a70e ]
LUCENE-9149: Increase data dimension limit in BKD
> Increase data dimension limit in BKD
> ------------------------------------
>
> Key: LUCENE-9149
> URL: https://issues.apache.org/jira/browse/LUCENE-9149
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Nick Knize
> Priority: Major
> Attachments: LUCENE-9149.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> LUCENE-8496 added selective indexing; the ability to designate the first K <=
> N dimensions for driving the construction of the BKD internal nodes. Follow
> on work stored the "data dimensions" for only the leaf nodes and only the
> "index dimensions" are stored for the internal nodes. While
> {{maxPointsInLeafNode}} is still important for managing the BKD heap memory
> footprint (thus we don't want this to get too large), I'd like to propose
> increasing the {{MAX_DIMENSIONS}} limit (to something not too crazy like 16;
> effectively doubling the index dimension limit) while maintaining the
> {{MAX_INDEX_DIMENSIONS}} at 8.
> Doing this will enable us to encode higher dimension data within a lower
> dimension index (e.g., 3D tessellated triangles as a 10 dimension point using
> only the first 6 dimensions for index construction)
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
