[
https://issues.apache.org/jira/browse/LUCENE-10321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461488#comment-17461488
]
ASF subversion and git services commented on LUCENE-10321:
----------------------------------------------------------
Commit ff274fddb656f119fde4f2c6637e7cbce82f191a in lucene's branch
refs/heads/branch_9x from Greg Miller
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=ff274fd ]
LUCENE-10321: Tweak MultiRangeQuery interval tree creation logic (#548)
> MultiRangeQuery doesn't need to "pull up" mins when building an interval tree
> -----------------------------------------------------------------------------
>
> Key: LUCENE-10321
> URL: https://issues.apache.org/jira/browse/LUCENE-10321
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/sandbox
> Reporter: Greg Miller
> Assignee: Greg Miller
> Priority: Trivial
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When creating an interval tree for the search intervals, the min values are
> being "pulled up" to keep internal node bounding boxes consistent. I don't
> believe this should be necessary though given the intersection/contains
> algorithms. I stumbled across this when comparing the impl to ComponentTree,
> which is serving a similar role for specialized 2D cases.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
