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/22 15:23:00 UTC

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=17496168#comment-17496168 ] 

Lu Xugang edited comment on LUCENE-10424 at 2/22/22, 3:22 PM:
--------------------------------------------------------------

{quote}but it actually works with fields that have multiple dimensions and/or that are multi-valued{quote}
Yes, but I am not sure why in the implementation of Weight#count , only 1D fields case was considered,  it seems count query can work on multi dimensions, please tell me if I missed something.

{quote}we limit this new case to single-valued 1D fields{quote}
If so, maybe we should support multi dimensions in Weight#count?



was (Author: chrislu):
??but it actually works with fields that have multiple dimensions and/or that are multi-valued??
Yes, but I am not sure why in the implementation of Weight#count , only 1D fields case was considered,  it seems count query can work on multi dimensions, please tell me if I missed something.

??we limit this new case to single-valued 1D fields??
If so, maybe we should support multi dimensions in Weight#count?


> 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
>            Assignee: Ignacio Vera
>            Priority: Minor
>             Fix For: 9.1
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> 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