[
https://issues.apache.org/jira/browse/LUCENE-10061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434299#comment-17434299
]
Adrien Grand commented on LUCENE-10061:
---------------------------------------
bq. in order to merge impacts from multiple fields for CombinedFieldsQuery, we
may need to compute all the possible summation combinations of competitive
{freq, norm} across all fields
I agree that there is a combinatorial explosion issue, and I fear that it's
even worse than the example that you gave since we also need to consider the
case when some fields do not match the query.
In the examples I've seen, there's often a field that has a much higher weight
than other fields (e.g. a title field that has a 10x greater weight than a body
field), so I am wondering if we could leverage this property to start from the
impacts of the field that has the highest weight and see how we can cheaply
incorporate impacts from other fields, even if this would overestimate the
actual maximum score for the query.
> CombinedFieldsQuery needs dynamic pruning support
> -------------------------------------------------
>
> Key: LUCENE-10061
> URL: https://issues.apache.org/jira/browse/LUCENE-10061
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
>
> CombinedFieldQuery's Scorer doesn't implement advanceShallow/getMaxScore,
> forcing Lucene to collect all matches in order to figure the top-k hits.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
