On Tue, Jan 29, 2013 at 7:39 PM, Sean Bridges wrote:
> How do we avoid similar situations in the future? Is Pulsing41PostingsFormat
> going to be maintained in future versions of Lucene? What are the
> safe PostingFormat/Codecs
> to use? Every PostingFormat/Codec is @deprecated or @experimenta
Thanks, we will try the class path trickery.
How do we avoid similar situations in the future? Is Pulsing41PostingsFormat
going to be maintained in future versions of Lucene? What are the
safe PostingFormat/Codecs
to use? Every PostingFormat/Codec is @deprecated or @experimental.
Sean
On Tue
Another option would be, using 4.0, use addIndexes(IndexReader[]) into
a new index, to convert your entire index into the supported (back
compat) codec (Lucene40).
Don't use addIndexes(Directory[]) as this just copies files.
Then you can read that resulting index with 4.1.
Mike McCandless
http:
Woops, sorry: PulsingPostingsFormat was already moved from core to
codecs as of 4.0 (not in 4.1 like I said before).
And ... yes, you need Pulsing40PostingsFormat on your classpath to
read your 4.0 indices with 4.1. I think you need to excise the
sources and get them on the classpath? But this w
Do I need the Pulsing40PostingsFormat class to read my indexes though?
Pulsing40PostingsFormat isn't shipped with lucene 4.1.
I have index files with names like _0_Pulsing40_0.frq. When I try to open
my index I get,
java.lang.IllegalArgumentException: A SPI class of type
org.apache.lucene.codecs
Pulsing41PostingsFormat was just moved out of core to the "codecs" module.
Still, the worst case (had it been deleted) would be to revive the
code from the past release and put it in your classpath, so old
indices could be read.
Mike McCandless
http://blog.mikemccandless.com
On Tue, Jan 29, 201
