[
https://issues.apache.org/jira/browse/LUCENE-7770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley moved SOLR-10445 to LUCENE-7770:
---------------------------------------------
Affects Version/s: (was: 5.6)
5.6
Security: (was: Public)
Component/s: (was: search)
core/codecs
Lucene Fields: New
Issue Type: Improvement (was: Bug)
Key: LUCENE-7770 (was: SOLR-10445)
Project: Lucene - Core (was: Solr)
> BloomFilteringPostingsFormat should implement seekExact(TermState) to avoid
> to seek within matching segment/field multiple times
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-7770
> URL: https://issues.apache.org/jira/browse/LUCENE-7770
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/codecs
> Affects Versions: 5.6
> Reporter: Yannis Hector
> Priority: Minor
>
> BloomFilteringPostingsFormat$BloomFilteredFieldsProducer$BloomFilteredTermsEnum
> does not reuse the TermState from the initial lookup when a second seek is
> issued (usually when we have a match and we build the Scorer).
> Default implementation of TermsEnum#seekExact(BytesRef term, TermState state)
> that is used by BF calls the regular seekExact method.
> This means that the BloomFilteringPostingsFormat default implementation
> performs a second lookup for every segment/field that have a match for the
> term (mostly in the various Weight#scorer implementations).
> I don't think it is a big issue as we mostly expect search terms to have a
> match in a limited number of segment/field. But for few queries it could
> become inefficient.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
