[
https://issues.apache.org/jira/browse/LUCENE-10424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496168#comment-17496168
]
Lu Xugang commented on LUCENE-10424:
------------------------------------
??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: [email protected]
For additional commands, e-mail: [email protected]
