Greg Miller created LUCENE-10321:
------------------------------------
Summary: 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
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: [email protected]
For additional commands, e-mail: [email protected]
