You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@lucene.apache.org by "Lu Xugang (Jira)" <ji...@apache.org> on 2022/02/18 03:34:00 UTC

[jira] [Updated] (LUCENE-10424) Optimize the "everything matches" case for count query in PointRangeQuery

     [ https://issues.apache.org/jira/browse/LUCENE-10424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lu Xugang updated LUCENE-10424:
-------------------------------
    Summary: Optimize the "everything matches" case for count query in PointRangeQuery  (was: Optimize the "everything matches" case for count queries in PointRangeQuery)

> Optimize the "everything matches" case for count query in PointRangeQuery
> -------------------------------------------------------------------------
>
>                 Key: LUCENE-10424
>                 URL: https://issues.apache.org/jira/browse/LUCENE-10424
>             Project: Lucene - Core
>          Issue Type: Improvement
>    Affects Versions: 9.1
>            Reporter: Lu Xugang
>            Priority: Minor
>
> In Implement of Weight#count in PointRangeQuery, Whether additional consideration is needed that when PointValues#getDocCount() == IndexReader#maxDoc() and the range's lower bound is less that the field's min value and the range's upper bound is greater than the field's max value, then return reader.maxDoc() directly?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org