[
https://issues.apache.org/jira/browse/LUCENE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignacio Vera resolved LUCENE-8990.
----------------------------------
Fix Version/s: 8.3
Assignee: Ignacio Vera
Resolution: Fixed
Thanks [~jpountz] and [~colings] for the help!
> IndexOrDocValuesQuery can take a bad decision for range queries if field has
> many values per document
> -----------------------------------------------------------------------------------------------------
>
> Key: LUCENE-8990
> URL: https://issues.apache.org/jira/browse/LUCENE-8990
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Ignacio Vera
> Assignee: Ignacio Vera
> Priority: Major
> Fix For: 8.3
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Heuristics of IndexOrDocValuesQuery are somewhat inconsistent for range
> queries . The leadCost that is provided is based on number of documents,
> meanwhile the cost() of a range query is based on the number of points that
> potentially match the query.
> Therefore it might happen that a BKD tree has millions of points but this
> points correspond to just a few documents. Therefore we can take the decision
> of executing the query using docValues and in fact we are almost scanning all
> the points.
> Maybe the cost() function for range queries need to take into account the
> average number of points per document in the tree and adjust the value
> accordingly.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
