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/28 10:32:00 UTC
[jira] [Commented] (LUCENE-10442) When indexQuery or/and dvQuery be a MatchAllDocsQuery then IndexOrDocValuesQuery should be rewrite to MatchAllDocsQuery
[ https://issues.apache.org/jira/browse/LUCENE-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498818#comment-17498818 ]
Lu Xugang commented on LUCENE-10442:
------------------------------------
Further more: can we leverage Weigh#count() to get a ConstantScoreScorer while count == reader.maxDoc() in implementation of Weight#scorerSupplier(LeafReaderContext context)?
If indexWeight.count(LeafReaderContext) or dvWeight.count(LeafReaderContext) equals reader.maxDoc() means match everything in this segment?
> When indexQuery or/and dvQuery be a MatchAllDocsQuery then IndexOrDocValuesQuery should be rewrite to MatchAllDocsQuery
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-10442
> URL: https://issues.apache.org/jira/browse/LUCENE-10442
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Lu Xugang
> Priority: Trivial
> Fix For: 9.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> IndexOrDocValuesQuery is typically useful for range queries, When indexQuery was rewrite to MatchAllDocsQuery and if IndexOrDocValuesQuery not be a lead iterator , it most likely that dvQuery will supply the Scorer not indexQuery.
--
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