[jira] [Updated] (LUCENE-4687) Lazily initialize TermsEnum in BloomFilterPostingsFormat

["Simon Willnauer (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LUCENE-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Willnauer updated LUCENE-4687:
------------------------------------

    Attachment: LUCENE-4687.patch

here is a patch... I also removed the IOException from Terms#comparator() to make it consistent with TermsEnum#comparator()
                
> Lazily initialize TermsEnum in BloomFilterPostingsFormat
> --------------------------------------------------------
>
>                 Key: LUCENE-4687
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4687
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/codecs
>    Affects Versions: 4.0, 4.1
>            Reporter: Simon Willnauer
>             Fix For: 4.2, 5.0
>
>         Attachments: LUCENE-4687.patch
>
>
> BloomFilteringPostingsFormat initializes its delegate TermsEnum directly inside the Terms#iterator() call which can be a pretty heavy operation if executed thousands of times. I suspect that bloom filter postings are mainly used for primary keys etc. which in turn is mostly a seekExact. Given that, most of the time we don't even need the delegate termsenum since most of the segments won't contain the key and the bloomfilter will likely return false from seekExact without consulting the delegate. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org