[
https://issues.apache.org/jira/browse/LUCENE-9114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048261#comment-17048261
]
Atri Sharma commented on LUCENE-9114:
-------------------------------------
I strongly believe that this is the right approach and we should be pursuing
this. I am actively working on this and will post a patch by Monday morning
> Add FunctionValues.cost
> -----------------------
>
> Key: LUCENE-9114
> URL: https://issues.apache.org/jira/browse/LUCENE-9114
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/query
> Reporter: David Smiley
> Priority: Major
>
> The FunctionRangeQuery uses FunctionValues.getRangeScorer which returns a
> subclass of ValueSourceScorer. VSC's TwoPhaseIterator has a matchCost impl
> that returns a constant 100. This is pretty terrible; the cost should vary
> based on the complexity of the ValueSource provided to FRQ. ValueSource's
> are typically nested a number of levels, so they should aggregate.
> BTW there is a parallel concern for FunctionMatchQuery which works with
> DoubleValuesSource which doesn't have a cost either, and unsurprisingly there
> is a TPI with matchCost 100 there.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
