[
https://issues.apache.org/jira/browse/LUCENE-8928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950628#comment-16950628
]
ASF subversion and git services commented on LUCENE-8928:
---------------------------------------------------------
Commit 0295e281d0498bdcd58ab023ad6dd9d8804a0815 in lucene-solr's branch
refs/heads/jira/SOLR-13731 from Ignacio Vera
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=0295e28 ]
LUCENE-8928: Compute exact bounds every N splits (#926)
When building a kd-tree for dimensions n > 2, compute exact bounds for an inner
node every N splits to improve the quality of the tree. N is defined by
SPLITS_BEFORE_EXACT_BOUNDS which is set to 4.
> BKDWriter could make splitting decisions based on the actual range of values
> ----------------------------------------------------------------------------
>
> Key: LUCENE-8928
> URL: https://issues.apache.org/jira/browse/LUCENE-8928
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently BKDWriter assumes that splitting on one dimension has no effect on
> values in other dimensions. While this may be ok for geo points, this is
> usually not true for ranges (or geo shapes, which are ranges too). Maybe we
> could get better indexing by re-computing the range of values on each
> dimension before making the choice of the split dimension?
--
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
