[
https://issues.apache.org/jira/browse/LUCENE-10446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500514#comment-17500514
]
Lu Xugang commented on LUCENE-10446:
------------------------------------
This is a new Query within the quick patch named NumericRangeQuery. It's
implementation is a simply merge that how PointRangeQuery,
IndexOrDocValuesQuery and IndexSortSortedNumericDocValuesRangeQuery supply a
Scorer.
Just wanner confirm if it is closed to LUCENE-10162's thought.
> Add a precise cost of score in ScorerSupplier
> ---------------------------------------------
>
> Key: LUCENE-10446
> URL: https://issues.apache.org/jira/browse/LUCENE-10446
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Lu Xugang
> Priority: Minor
> Attachments: LUCENE-10446.patch, LUCENE-10466-1.patch
>
>
> Some queries could sometime actually provide a precise cost of Score like
> RangeFieldQuery, PointRangeQuery, SpatialQuery. maybe we could do some
> optimization by using this precise cost.
> Like in IndexOrDocValuesQuery, when indexScorerSupplier or/and
> dvScorerSupplier's precise cost is reader.maxDoc, we will supply the right
> Scorer instead of according to the condition of threshold <= leadCost which
> sometime supply a inappropriate Score when IndexOrDocValuesQuery not a lead
> iterator.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
