lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Harwood (JIRA)" <>
Subject [jira] [Commented] (SOLR-3950) Attempting postings="BloomFilter" results in UnsupportedOperationException
Date Tue, 16 Oct 2012 08:43:03 GMT


Mark Harwood commented on SOLR-3950:

BloomFilterPostingsFormat is designed to wrap another choice of PostingsFormat and adds ".blm"
files to the other files created by the choice of delegate.

However your code has instantiated a BloomFilterPostingsFormat without passing a choice of
delegate - presumably using the zero-arg constructor. 
The comments in the code for this zero-arg constructor state:

  // Used only by core Lucene at read-time via Service Provider instantiation -
  // do not use at Write-time in application code.

> Attempting postings="BloomFilter" results in UnsupportedOperationException
> --------------------------------------------------------------------------
>                 Key: SOLR-3950
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.1
>         Environment: Linux bigindy5 #1 SMP Wed
Sep 26 03:52:55 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> [root@bigindy5 ~]# java -version
> java version "1.7.0_07"
> Java(TM) SE Runtime Environment (build 1.7.0_07-b10)
> Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode)
>            Reporter: Shawn Heisey
>             Fix For: 4.1
> Tested on branch_4x, checked out after BlockPostingsFormat was made the default by LUCENE-4446.
> I used 'ant generate-maven-artifacts' to create the lucene-codecs jar, and copied it
into my sharedLib directory.  When I subsequently tried postings="BloomFilter" I got a the
following exception in the log:
> {code}
> Oct 15, 2012 11:14:02 AM org.apache.solr.common.SolrException log
> SEVERE: java.lang.UnsupportedOperationException: Error - org.apache.lucene.codecs.bloom.BloomFilteringPostingsFormat
has been constructed without a choice of PostingsFormat
> {code}

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message