[
https://issues.apache.org/jira/browse/LUCENE-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17441582#comment-17441582
]
Lu Xugang commented on LUCENE-10120:
------------------------------------
{quote}If the use-case you are interested in is counting matches for range
queries on 1D fields, there is an open issue around changing the Points API and
then implementing Weight#count on PointRangeQuery so that we could count
matches for single-valued fields without running the query{quote}
Thanks, [~jpountz].
{quote}Maybe we could improve these cases via rewrite rules instead?{quote}
Really good idea. TermRangeQuery can be easily rewrite to a MatchAllDocsQuery,
beacuse firstPendingTerm(smallest term) and lastPendingTerm(biggest term) in
.tim index file. And so is PointRangeQuery, because minPackedValue and
maxPackedValue in .kdm index file.
> Lazy initialize FixedBitSet in LRUQueryCache
> --------------------------------------------
>
> Key: LUCENE-10120
> URL: https://issues.apache.org/jira/browse/LUCENE-10120
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Affects Versions: main (10.0)
> Reporter: Lu Xugang
> Priority: Major
> Attachments: 1.png, LUCENE-10120.patch
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> Basing on the implement of collecting docIds in DocsWithFieldSet, may be we
> could do similar way to cache docIdSet in
> *LRUQueryCache#cacheIntoBitSet(BulkScorer scorer, int maxDoc)* when docIdSet
> is density.
> In this way , we do not always init a huge FixedBitSet which sometime is not
> necessary when maxDoc is large
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
