kkewwei commented on PR #16089:
URL: https://github.com/apache/lucene/pull/16089#issuecomment-5118817824
@epotyom Very thank you for your review, sorry for my delayed reply.
You're right, my previous “at most two crossing leaves” argument only
applies to one-dimensional range queries. In multiple dimensions, many leaves
may cross the query boundary and `estimateDocCount()` may trigger an eager
FixedBitSet allocation even when the actual result is sparse.
I haven't found a robust way to solve it, how about restrict to
one-dimensional `PointRangeQuery` and remove it from `SpatialQuery` and
`PointInSetQuery`.?
```
// PointRangeQuery
if (cost != -1 && numDims == 1) {
result.expectMore(cost);
}
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
